docs(drift): draft from internal source

[pedromcunha]

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

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
unevenlabs	🟢 Ready	View Preview	Sep 8, 2026, 3:37 PM

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

[github-actions]

Claude finished @pedromcunha's task in 2m 8s —— View job

---

Code review

The diff is a single row deletion — gunz (chain id 43419) removed from the depository address table in references/protocol/depository/addresses.mdx:56. The table formatting, id ordering, and column padding all stay intact, and nothing else in the repo mentions gunz/43419, so there are no dangling references. references/protocol/ is explicitly out of scope for AGENTS.md v1 (§1.1), and the change pattern-matches the previous drift PR on this file (#438 removed degen the same way), so there are no style findings.

The substantive issue is with the target file, not the edit.

---

1. This edit is a no-op on the published docs — the page it touches is retired

references/protocol/depository/addresses.mdx is not in the navigation, and docs.json:520-523 redirects its route away:

{
  "source": "/references/protocol/depository/addresses",
  "destination": "/references/protocol/addresses"
}

The live surface is references/protocol/addresses.mdx:31, which renders <Depositories id="mainnetDepositories" env="mainnets" />. That snippet fetches https://api.relay.link/chains in the browser and filters on chain.protocol.v2.depository (snippets/Depositories.mdx) — exactly the query the static table's generation comment (references/protocol/depository/addresses.mdx:7) documents. So a reader already sees gunz gone without this PR, and the hand-maintained copy is a stale duplicate that generates a manual drift PR every time a chain is added or dropped (twice in the last ~week).

Worth deciding at the source: either delete the stale file (the redirect already covers inbound traffic) or fix the drift automation so it stops targeting it. Merging as-is is harmless but keeps the churn.

Fix this →

2. Two inbound links point at the redirected path (pre-existing, low severity)

references/protocol/guides/for-apps.mdx:67 and :69 both link to [Contracts Addresses](/references/protocol/depository/addresses). They resolve via the redirect, but they should point at /references/protocol/addresses — and they become the blocker if the stale file is deleted.

Fix this →

---

Verification limit

I could not confirm the removal against the source of truth: outbound network calls to https://api.relay.link/chains are not permitted in this job, so whether gunz still returns a protocol.v2.depository is unverified here. On the rendered page this doesn't matter (finding 1 — the list is fetched client-side), but if the static table is kept, that row deletion is taken on trust from the source PR.

PR checklist

• Content matches shipped behavior — unverifiable offline (see above); no internal-only details leaked.
• CLAUDE.md conformance — n/a, references/protocol/ is out of §1.1 scope; edit matches surrounding rows.
• Cross-references — no gunz references anywhere in the repo; the two for-apps.mdx links above are pre-existing.

No changes pushed — this was a review.
· branch docs-drift/src-6d18328241-c8de149

[greptile-apps]

Confidence Score: 5/5

Safe to merge: the sole documentation removal matches the current Relay chains data.

What we checked:

• Executed the Relay chains API comparison to align document revisions with the live API by running the Python comparison script.
• Reviewed the base depository state before the PR, which showed a gunz row that is not present in the live API.
• Reviewed the head depository state after the PR, confirming no gunz or 43419 entries remain in either the API or the head table.
• Verified that the executable check source demonstrates a reproducible workflow fetching the live API and running the comparison.

Summary

• This change removes the obsolete Gunz depository-contract row for EVM chain ID 43419 from the address reference. The table was compared with Relay’s live chains API: the API no longer returns a gunz chain or chain ID 43419, and the updated reference no longer lists either value. The change aligns the published documentation with the current supported-chain data and is safe to merge.

_{Reviews (1) · Last reviewed commit: "docs(drift): draft from internal source"}