docs(drift): draft from internal source

[pedromcunha]

Drafted from an internal source repo, requested by @tv3636.

This PR was auto-generated by the reusable-docs-draft-pr workflow from a Claude-drafted update in the source repo. It is opened as a draft — please review, edit as needed, and mark ready for review before merging.

Review checklist

• Content matches the behavior shipped in the source PR
• No internal-only details (service names, file paths, unreleased names, security internals) leaked into the draft
• Conforms to CLAUDE.md style rules
• Cross-references and internal links resolve
• Any Needs human input items from the source comment are addressed

---

Generated by reusable-docs-draft-pr.yml in relayprotocol/agents-config.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
unevenlabs	🟢 Ready	View Preview	Sep 1, 2026, 2:23 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[github-actions]

Claude finished @tv3636's task in 1m 57s —— View job

---

Code review — PR #438

Reviewed the two deletions (removing Degen chain traces). Both changes are directionally right, but one leaves a documentation gap and the other lands on a file readers never see.

---

1. The onramp section loses its only toAddress example — references/api/api_guides/deep-linking.mdx

The deleted block was the sole example demonstrating the toAddress query param for the onramp page. After this PR, ### Examples under Deep Linking to the Onramp Page contains exactly one entry (Onramp onto Base with Base DEGEN), which only demonstrates toCurrency — while the parameter table two lines above still documents toAddress (references/api/api_guides/deep-linking.mdx:125).

That's out of step with the two sibling sections on the same page, which both keep a "with a preset address" example:

• Bridge page — deep-linking.mdx:35-42
• Dedicated chain pages — deep-linking.mdx:92-99

The chain slug is the only part of the URL that went stale; the param itself is unaffected. Rewriting the example onto a supported chain preserves the coverage:

#### Onramp onto Base with a preset address

<a
	href={`https://relay.link/onramp/base?toAddress=0x03508bB71268BBA25ECaCC8F620e01866650532c`}
	target="_blank"
>
	`https://relay.link/onramp/base?toAddress=0x03508bB71268BBA25ECaCC8F620e01866650532c`
</a>

Fix this →

2. The addresses.mdx edit is a no-op — readers never see that file

references/protocol/depository/addresses.mdx is a retired page:

• It is not in navigation in docs.json.
• docs.json:520-523 redirects /references/protocol/depository/addresses → /references/protocol/addresses.

The live page (references/protocol/addresses.mdx:29-31) doesn't hardcode depository addresses at all — it renders <Depositories id="mainnetDepositories" env="mainnets" />, which the page itself describes as "fetched live from the Chains API and stays in sync as new chains are added." So the reader-facing address table already dropped Degen the moment the API did; no doc edit was needed, and this one changes nothing that ships.

Not a reason to block — the edit is harmless. But it's worth knowing the drift tooling is editing a dead file, since it'll keep doing so. The real cleanup is deleting the stale depository/ tree (addresses.mdx plus contracts/, both of which have redirects at docs.json:513-523 pointing at their live replacements), which is out of scope for this PR.

I checked the same question for the other chain lists: references/api/api_resources/supported-chains.mdx also renders live via <Chains />, so it needs no edit either. A repo-wide case-insensitive search for degen turns up nothing else besides codegen matches.

---

Looks right

• Keeping #### Onramp onto Base with Base DEGEN is correct. That example points at 0x4ed4e862860bed51a9570b96d89af5e1b0efefed — the DEGEN token on Base, not the Degen chain. Removing the chain shouldn't touch it. Worth a quick confirmation against the source PR that the token stayed supported, but on its face the split is right.
• Deletion-only diff; no style-guide (AGENTS.md) violations introduced. Nothing internal-only leaked.

One question for the author

Does a user-visible chain removal warrant an .changelog/app.md entry (**Removed**) per §4.2? That file is explicitly "curated copy… add an entry when there is something worth announcing," so this is your call rather than a rule — but chain lists elsewhere are API-driven, meaning the changelog is the only place this would be announced.

---

• Gather PR diff
• Check for orphaned Degen references across the docs
• Verify style-guide conformance
• Post review

Review only — no changes pushed.
· docs-drift/src-2203e69aef-f7cbd65

[greptile-apps]

Greptile Summary

This change removes obsolete Degen-chain documentation from the onramp deep-link examples and the Depository contract-address table. A live check of the Relay chains endpoint confirmed that Degen is no longer returned, and the updated contract-address table no longer lists it. No issues were found.

Confidence Score: 5/5

Safe to merge: the removed Depository entry now matches the live Relay chain catalog.

The live Relay chains response was captured successfully and compared against both the previous and updated address tables. It confirmed that the prior Degen row was stale and that the updated table is aligned with the source it documents.

Files Needing Attention: No files need further attention.

T-Rex Logs

What T-Rex did

• Ran a live GET request to https://api.relay.link/chains and captured HTTP/2 200, then ran the uploaded Degen Depository table comparison script against the parent MDX and the updated MDX; the parent table contained a Degen row while the live response did not, confirming that removing Degen from the MDX aligns the documentation with the current chain catalog.
• Validated that after removal, the MDX reports mdx_degen_row_present: False and the API endpoint reports endpoint_degen_present: False, while the chains endpoint still returns HTTP/2 200.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "docs(drift): draft from internal source" | Re-trigger Greptile}