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 (UTC)
unevenlabs	🟢 Ready	View Preview	Aug 3, 2026, 4:54 PM

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

[github-actions]

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

---

Code review — PR #396

• Read the diff (git diff origin/main...HEAD)
• Check the changed file for ordering/consistency
• Check for stale references to the removed chain elsewhere in the docs
• Post review

The whole PR is one deleted row in references/protocol/depository/addresses.mdx — the zero chain (0xa88cf7864951147a08707ed732237eaa9b1c3b9b, chain id 543210). Table ordering, alignment, and the surrounding rows are all clean; nothing else in the repo referenced that chain or that address, so there are no dangling links to fix.

Two things worth deciding before merge, plus one caveat about what I could verify.

---

1. The table is generated — a hand-edited single row leaves the rest unverified

references/protocol/depository/addresses.mdx:7 declares its own provenance:

{/* Generated using: "curl https://api.relay.link/chains | jq '.chains[] | "|\(.protocol.v2.chainId)|\(.protocol.v2.depository)|\(.vmType)|\(.id)"" */}

The last content change to this page before this PR was 1fea003 ("Update audit links"), so the table body hasn't been refreshed in a while. If zero disappeared from /chains upstream, other drift very likely accumulated in the same window — chains added, or a protocol.v2.depository that moved. A surgical one-row delete makes the page less wrong without making it right, and the diff gives a reviewer no signal either way.

Suggest re-running the documented command and committing the full regenerated table, so this page matches the API as a whole rather than in one spot. Fix this →

2. Dropping a supported chain is integrator-visible — consider a changelog entry

Per AGENTS.md §4.4, a change that alters observable behavior (here: quotes and requests referencing chain 543210 stop working) gets an entry in the product's changelog source, and §4.2 names references/api/changelog.mdx as the source for the API line. references/protocol/ is out of §1.1 scope for the style guide, but the playbooks in §4 key off the change, not the page it lands on.

Related: after this PR the Zero depository address appears nowhere in the docs. If the chain is being sunset rather than having never shipped, anyone reconciling a past deposit onchain loses the only published record of the contract they deposited into. A one-line **Deprecated** / **Breaking** changelog entry naming the chain and the address would preserve that without keeping a dead row in a live support table. Your call on whether Zero was public-facing enough to warrant it.

3. I could not verify the underlying claim

Network egress is blocked in this environment (both the curl and a WebFetch against https://api.relay.link/chains were denied), so I can't confirm that zero is in fact gone from /chains, nor that the remaining 69 rows still match. That check is the one that matters most for a generated table, and it needs a human or a run with network access. Reviewer checklist item "Content matches the behavior shipped in the source PR" is unverified from my side.

---

Nothing blocking on style. No internal-only details are exposed by a deletion, frontmatter is untouched, and the page needs no §2 changes.
· docs-drift/src-6c624ef57e-a43e40a

[github-actions]

Claude finished @pedromcunha's task in 5m 25s —— View job

---

Code review — PR #396

• Gather context (diff, docs.json, successor page, related history)
• Understand the request (/code-review)
• Review and verify findings
• Post review

---

Scope: one line. Commit 8dca003 deletes the zero row (chain id 543210, depository 0xa88cf786…) from references/protocol/depository/addresses.mdx. Nothing else changed.

Headline: the edit lands on a page that is no longer a published surface, so it cannot have the effect it appears to have.

1. The edited page is retired and redirected away — the change is a no-op for readers

docs.json:511-514 redirects /references/protocol/depository/addresses → /references/protocol/addresses. Every one of the seven references/protocol/depository/* paths appears in docs.json only as a redirect source; none are in navigation. The successor page renders the depository table live:

The list below is fetched live from the [Chains API](https://api.relay.link/chains) and stays in sync as new chains are added.

<Depositories id="mainnetDepositories" env="mainnets" />

_{references/protocol/addresses.mdx:29-31}

Published docs are byte-identical before and after this PR, and chain add/remove needs no doc edit at all. Note the restructure cleanup was partial — overview/architecture/security were deleted, but addresses.mdx, contracts/*, and guides/integrating.mdx were left behind, which is how a drafting agent found this file at all.

Fix this →

2. The table is a pre-#298 snapshot — removing one row leaves ~33 other errors

eed0fcf ("Refresh depository contract addresses from live Chains API", #298, 2026-07-22) already declared this data stale and rewrote the successor table. Against that commit's own summary, the file this PR edits still carries:

• 12 chains the API no longer returns — xai (:71), forma (:73), plus funki, mint, appchain, polygon_zkevm, gravity, sanko, hychain, powerloom, arena_z, onchain_points
• 13 supported chains missing — monad, stable, hyperliquid, tempo, megaeth, plasma, mythos, doma, gensyn, lighter, ethereal, tron
• 8 outdated slugs — bnb→bsc, manta→manta-pacific, worldchain→world-chain, flow→flow-evm, b3→B3, arbitrum_nova→arbitrum-nova, anime→animechain, zero→zero-network
• a wrong deposit address — references/protocol/depository/addresses.mdx:75 still shows bc1qdqqsq6y7csd0cr3ye45h9lv8ydh777j2wehgl6 for bitcoin; eed0fcf replaced it with 1KT3zCYUrmQxjcveUNs1Rs7WcXDcPQZ4av

A stale table with an incorrect deposit address is the real risk on this page, and it survives this PR untouched.

3. Repo evidence contradicts the premise: Zero looks renamed, not de-supported

eed0fcf lists zero under renames (zero → zero-network), not under the 12 chains the API dropped. And changelog.mdx:27 adds Zero placeholder-address recognition to the SDK (7.0.2 / UI Kit 11.0.3) — eleven days after this commit was drafted. Both point to Zero still being supported under a new slug.

Confidence: plausible, not confirmed — I could not reach api.relay.link/chains from the sandbox. The source PR should cite the API response that justifies the removal.

Recommendation

Close this in favor of deleting the orphaned references/protocol/depository/*.mdx files. If Zero support genuinely ended, the reader-facing record is a changelog entry per AGENTS.md §4.2 — the changelog is the record for removals, not an unreachable table.

Style-wise there's nothing to flag: the diff touches no prose, and §2/§3 rules don't bite on a table-row deletion.

--- · Branch: docs-drift/src-6c624ef57e-a43e40a

[greptile-apps]

Greptile Summary

This change removes the retired Zero chain from the depository-address reference. Verification against Relay's live chain registry found that the same reference still lists an outdated Bitcoin depository address and omits the active Hyperliquid and Lighter depository entries, leaving integrators without complete current deposit destinations.

Confidence Score: 4/5

The documentation update should not merge until the generated address table is refreshed from the current chain registry.

A live comparison directly exercised the generator source named in the document and reproduced the incorrect Bitcoin address and the missing Hyperliquid and Lighter entries.

Files Needing Attention: references/protocol/depository/addresses.mdx needs regeneration from https://api.relay.link/chains.

T-Rex Logs

What T-Rex did

• T-Rex generated a reproducible MDX vs live Relay API comparison script to validate the P1 finding.
• T-Rex captured and reviewed the MDX vs live Relay API comparisons, including the parent comparison, the checked-out comparison, and the PR diff for the depository address table.
• T-Rex performed general contract validation by running the Python-based MDX vs live API checks, retrieving the live endpoint data, and documenting mismatches between live data and the MDX table for Bitcoin, Hyperliquid, and Lighter.
• T-Rex attached and organized the supporting artifacts for both proofs to enable reviewer inspection.

_{Ran code and verified through T-Rex}

Comments Outside Diff (2)

1. references/protocol/depository/addresses.mdx, line 75 (link)

   Generated depository-address table is stale

   The table no longer matches the /chains response named in its generation comment: Bitcoin is documented as bc1qdqqsq6y7csd0cr3ye45h9lv8ydh777j2wehgl6, but the live depository is bc1qzmtn0q92ayejt2hpffvlktcpmyy7vvsd06sefu. Hyperliquid (0x66cf0aace1b4e562593bec10ec7868fba9932224, hypevm, 1337) and Lighter (731033, lvm, 3586256) also have non-empty live depositories but no rows. Regenerate the table from the current endpoint rather than removing only the retired chain so integrators receive usable deposit destinations.

   Artifacts

   
   

   Reproducible live Relay API and MDX comparison script

   • This script retrieves the live chains endpoint, reads the MDX table, and compares Bitcoin, Hyperliquid, and Lighter depository values; it provides a repeatable check of the discrepancy.

   Parent MDX comparison against live Relay API

   • The executed comparison against the parent MDX records the same Bitcoin mismatch and missing Hyperliquid and Lighter rows before the PR's Cyber-row removal, showing the claimed defect is pre-existing.

   Checked-out MDX comparison against live Relay API

   • The executed comparison against the checked-out MDX records the live values and the Bitcoin mismatch plus absent Hyperliquid and Lighter rows, confirming the table is stale.

   PR diff for the depository address table

   • The captured diff shows this PR removes only the `cyber` row, so it neither fixes nor introduces the three live API comparison failures.

   

   _{Ran code and verified through T-Rex}

2. General comment

   Generated depository-address table is stale for Bitcoin and omits Hyperliquid and Lighter

   • Bug
     • The checked-out table does not reflect the live API fields it declares as its generator source. Bitcoin's documented address differs from the live depository, while Hyperliquid and Lighter have non-empty live protocol.v2.depository values but no table row.
   • Cause
     • The table was not regenerated from the current /chains response after the allocator/depository values changed.
   • Fix
     • Regenerate references/protocol/depository/addresses.mdx from https://api.relay.link/chains using the documented fields, which updates Bitcoin to bc1qzmtn0q92ayejt2hpffvlktcpmyy7vvsd06sefu and adds Hyperliquid (0x66cf0aace1b4e562593bec10ec7868fba9932224, hypevm, 1337) and Lighter (731033, lvm, 3586256).

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "Merge branch 'main' into docs-drift/src-..." | Re-trigger Greptile}