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:29 PM

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

[github-actions]

Claude finished @pedromcunha's task in 1m 45s —— View job

---

Code review — PR #448

• Gather context (diff, changed file, repo-wide references)
• Check style-guide conformance (AGENTS.md)
• Check for dangling references and precedent
• Post review

---

No findings. This is a clean, minimal change.

Scope

One line removed from the generated depository address table — the gunz row (EVM chain id 43419) at references/protocol/depository/addresses.mdx:57. Nothing else in the commit.

-| gunz           | 0x4cd00e387622c35bddb9b4c962c136462338bc31   | ethereum-vm | 43419        |

What I checked

• No dangling references. Repo-wide case-insensitive search for gunz and 43419 returns nothing, so the removal leaves no orphaned links, nav entries, or prose mentions.
• Table structure intact. Header and alignment rows untouched; ordering by EVM chain id stays monotonic across the deletion (43114 → 48900).
• Matches established precedent. fc97f36 (PR docs(drift): draft from internal source #438) removed the degen row from this same generated table in exactly this shape — a bare row deletion, not a deprecation marking. references/protocol/ is also out of scope for the AGENTS.md v1 profiles (§1.1), where the rule is to pattern-match against existing pages in the folder; this does.
• No chain-count claims invalidated. The 85+ chains / 80+ chains figures in solutions/*.mdx and references/protocol/overview.mdx are approximate and already above the table's row count. references/api/api_resources/supported-chains.mdx and contract-addresses.mdx render from the <Chains> / <Contracts> snippets rather than a static list, so they need no companion edit.

One item for you, not a defect

The table is generated from curl https://api.relay.link/chains (see the comment at line 7), and I have no network access in this run to confirm gunz has actually been dropped from .chains[]. Your checklist item "Content matches the behavior shipped in the source PR" still needs a human to verify that against the live API or the internal source PR.

Related: a full regeneration would capture all drift at once, whereas this draft changes only the one row. If other chains were added or removed in the same window, they aren't reflected here. Worth a glance if the last regeneration was a while ago.
• Branch: docs-drift/src-54db283871-7d0e058

[greptile-apps]

Confidence Score: 5/5

Safe to merge: the updated contract-address reference matches the currently returned Relay chain data.

Summary

• Removes the obsolete Gunz depository address mapping for EVM chain ID 43419 from the Relay Protocol contract-address reference.
• The live https://api.relay.link/chains response was checked and returned no Gunz or chain-ID-43419 mapping, while the updated table also omits it. This confirms the documentation now reflects the current Relay chain list. No issues were found.

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