Docs refresh + dedicated Wormhole section for EVM developers

[vriveraPeersyst]

Summary

This PR refreshes stale content across the portal, adds a dedicated Wormhole section, and applies a sitewide style cleanup. Every Wormhole guide was verified end-to-end on-chain before documenting it.

New Wormhole section

Reference (Bridge section, mirroring the Axelar layout):

• Overview (pages/bridge/wormhole/): architecture (Guardians, VAAs, Executor), Wormhole chain ID 57 vs EVM chain IDs, supported products matrix, XRPL (chain 66) status
• Deployed Contracts: Core, WTT, Executor, Guardian Governance addresses for Mainnet/Testnet, with the testnet-only legacy relayer warning
• Supported Tokens: tokens verified live on each network (XRP via the native ERC20 sentinel, RLUSD and USDC.e via NTT, WETH via WTT)

Hands-on guides (Developers > Advanced Guides > Cross-Chain Transactions > Wormhole):

• Send Cross-Chain Messages (Solidity, Core Contract + Executor delivery)
• Transfer Tokens (TypeScript SDK + Portal Bridge)
• Native Token Transfers (NTT CLI deployment flow)
• Connect Widget (React integration)

On-chain verification behind the guides

• Deployed the messaging contracts on Testnet, published a message, retrieved the guardian-signed VAA from WormholeScan, verified it in the receiver (replay protection included)
• Ran the TS SDK transfer flow (approve + transfer + attestation); confirmed tokenId("XRPLEVM", "native") reverts (WTT WETH() unset) and that XRP bridges through its sentinel ERC20 instead
• Deployed an NTT manager on Testnet with the NTT CLI (chain name XRPLEVM)
• Confirmed the wormhole-solidity-sdk v1.0.0 interface is ICoreBridge (no IWormhole.sol), and that RLUSD/USDC.e NTT managers are mutually peered with their canonical Ethereum counterparts
• Read-only checks on Mainnet: all contract addresses, chain IDs, guardian sets, and the absence of an official legacy relayer

Docs refresh

• EVM compatibility notice updated: Cosmos EVM migration shipped (Prague, solc up to 0.8.30) — verified via Pectra BLS precompiles on both networks
• Node versions v10.0.2/v10.0.1 -> v10.1.0 (live network version)
• Fixed Mainnet MetaMask tab showing the Testnet RPC URL in the deploy guide
• Replaced dead hosts (cosmos.xrplevm.org:1317/26657, bridge*.xrplevm.org) with live endpoints
• Deduplicated the IBC channel tables into shared snippets; fixed copy-pasted frontmatter blurbs; flagged the manual-relay guides as devnet-amplifier examples

Style cleanup

• All emojis removed (support tables now use Yes/No/In progress)
• Em/en dash punctuation rewritten as standard punctuation; unicode hyphens normalized
• Users section opening lines rewritten
• Full-branch review pass fixing rendering breakers (Markdoc tags swallowed into tables, tab renumbering, indentation damage) and content bugs (wrong RPC host, anchor links, frontmatter slug collision)

🤖 Generated with Claude Code

[oeggert]

Mostly looks good, but there are broken links to address, as well as some minor front matter issues.

[oeggert]

Suggested change

	blurb: Wormhole contract addresses on the XRPL EVM Sidechain.
	seo:
	description: Wormhole contract addresses on the XRPL EVM Sidechain.

blurb isn't a valid frontmatter used by redocly.

[vriveraPeersyst]

Good catch, and blurb turned out to be worse than invalid — it is inert. The live pages carry no <meta name="description"> at all and the blurb string appears nowhere in the rendered HTML; nothing in redocly.yaml, theme.ts or @theme reads it.

labels, html and status are dead in exactly the same way, so I removed all four across the 15 files that had them rather than leave the same dead keys in pages this review did not happen to open.

One deviation from your suggestion: I kept the field you asked for but not the text. Since these become real meta descriptions, I wrote each one against the page content instead of reusing the blurb — 141-151 chars, unique across the set. Here it is:

seo:
  description: "Wormhole contract addresses on the XRPL EVM Sidechain: Core Contract, Wrapped Token Transfers, Executor and Guardian Governance, per network."

Note the quotes. Six of the new descriptions contain a colon-space, which YAML parses as a nested mapping and which broke the frontmatter until quoted — probably worth keeping quoted as a convention for this field.

Fixed in 7829d03.

[oeggert]

Suggested change

	blurb: Wormhole interoperability on the XRPL EVM Sidechain.
	seo:
	description: Wormhole interoperability on the XRPL EVM Sidechain.

[vriveraPeersyst]

Applied, with the same deviation as on deployed-contracts.md: correct field, rewritten text.

seo:
  description: "Wormhole on the XRPL EVM Sidechain: how Guardians, VAAs and the Executor connect XRPL EVM to 40+ chains for cross-chain messaging and transfers."

Fixed in 7829d03.

[oeggert]

Suggested change

	blurb: Tokens supported by Wormhole on the XRPL EVM Sidechain.
	seo:
	description: Tokens supported by Wormhole on the XRPL EVM Sidechain.

[vriveraPeersyst]

Applied, same as the other two.

seo:
  description: "Tokens Wormhole supports on the XRPL EVM Sidechain, including XRP, RLUSD, USDC.e and WETH, with addresses, transfer mechanism and connected chains."

Fixed in 7829d03.

[oeggert]

Suggested change

	{% partial file="/snippets/_ibc-channels-mainnet.md" /%}

[vriveraPeersyst]

Done, and I did the Testnet table below it too — both were inline copies of snippets this branch had already created.

One thing worth flagging for whoever touches this file next: I left the partial tags at the tab's 6-space indentation rather than moving them to column 0 like the other call sites. Realm dedents a tag body by its common indent, so a single line at column 0 would drop the common indent to zero and turn the rest of the tab into an indented code block.

Fixed in a2fe7c6.

[oeggert]

This links 404s

[vriveraPeersyst]

Confirmed 404. docs.cosmos.network moved its SDK docs under a /sdk/ prefix, so every /v0.50/... path on the old host is gone. Six links in this file were affected, not just this one.

All rewritten to /sdk/v0.50/learn/advanced/grpc_rest, and I checked that the #grpc-server, #rest-server and #cometbft-rpc anchors still exist in the new page rather than assuming they carried over.

The same move had broken two more links on the branch that were outside your review: the cosmovisor link in upgrading-your-node.md and two /v0.52/learn/intro/ links in interacting-with-cosmos/introduction.md. Fixed in the same commit.

Fixed in a2fe7c6.

[oeggert]

Link is broken

[vriveraPeersyst]

Worse than broken — chains.tools no longer resolves at all (NXDOMAIN), so there is no replacement URL to point at. I removed the entry rather than leave a dead faucet listed.

The Devnet tab still has the faucet.xrplevm.org entry above it, which covers Devnet via the network selector, so the tab is not left empty.

Fixed in a2fe7c6.

[oeggert]

This link 404s

[vriveraPeersyst]

Thanks for catching this — chasing the 404 turned up a bigger problem. The URL was not stale, the whole recipe was fictional: there is no SquidWidget.init() global and no script-tag distribution in any release of the widget. Anyone following this page would never have gotten it working.

Rewritten against the real integration: npm install @0xsquid/widget and the <SquidWidget config={...} /> React component, with the Integrator ID prerequisite called out (Squid issues it per project and it gates which chains you can route), a note on the native-token sentinel address, and pointers to the Next.js/Vite setup guides.

Also added a no-code section linking the hosted bridge with XRPL EVM preselected, for readers who do not need it embedded.

Fixed in a2fe7c6.

[oeggert]

Getting a specified key doesn't exist error

[vriveraPeersyst]

Same fix as the Mainnet row — exrpd_latest.tar.lz4. This one is a real 9.9 GB archive, though it was last regenerated on 2026-05-06, so it is about three months stale. Same conversation with the bucket owners as in the thread above.

Fixed in a2fe7c6.

[vriveraPeersyst]

Correction to my earlier comment, and an update.

The bucket moved: the archives are now published at xrpl-evm-snapshots.s3.us-east-1.amazonaws.com/{mainnet,testnet,devnet}.tar.lz4, all three live and current. Both files are updated, and Devnet now has a real snapshot row instead of the "none available" note.

I also need to walk back what I said about the old Mainnet archive. I claimed 79 MB could not be a usable snapshot for a chain at that height. That was an inference from file size and it was wrong — I downloaded the current one and inspected it: 170 MB uncompressed, of which 168.6 MB is application.db and 0.3 MB is blockstore.db, with a .state_sync_done marker. It is generated from a state-synced node, so it carries full state and no block history, which is exactly why it is small. The old archive was almost certainly the same thing.

What was actually wrong stands: the documented URL 404'd and the file was four months stale. Sorry for the noise on the diagnosis.

Updated in 0a18d23.

[oeggert]

Getting a specified key doesn't exist error

[vriveraPeersyst]

Confirmed — the archives are published as exrpd_latest.tar.lz4; the exrpd.tar.lz4 key you hit returns NoSuchKey. Both rows updated, and installing-the-node.md carried the same dead URL inside its wget commands, so that is fixed in the same commit.

Flagging one thing this does not fix, so the green link does not read as all-clear: the Mainnet bucket holds a single object, 79 MB, last modified 2026-04-22. For a chain around block 7.37M that cannot be a usable snapshot — Testnet's equivalent is 9.9 GB. So the 404 is gone but an operator following this row would still fail, just later and less obviously.

I have raised it with the team that owns the bucket. If the generation job is dead and not coming back, the honest fix is to drop the Peersyst row and leave Polkachu/Cumulo/ITRocket. Happy to do that in this PR if you would rather not merge a row that is broken in substance.

Fixed in a2fe7c6.

[vriveraPeersyst]

Correction to my earlier comment, and an update.

The bucket moved: the archives are now published at xrpl-evm-snapshots.s3.us-east-1.amazonaws.com/{mainnet,testnet,devnet}.tar.lz4, all three live and current. Both files are updated, and Devnet now has a real snapshot row instead of the "none available" note.

I also need to walk back what I said about the old Mainnet archive. I claimed 79 MB could not be a usable snapshot for a chain at that height. That was an inference from file size and it was wrong — I downloaded the current one and inspected it: 170 MB uncompressed, of which 168.6 MB is application.db and 0.3 MB is blockstore.db, with a .state_sync_done marker. It is generated from a state-synced node, so it carries full state and no block history, which is exactly why it is small. The old archive was almost certainly the same thing.

What was actually wrong stands: the documented URL 404'd and the file was four months stale. Sorry for the noise on the diagnosis.

Updated in 0a18d23.

[vriveraPeersyst]

@oeggert all nine threads are addressed — replies inline on each. Two commits, and since the diff grew past what you reviewed, here is the scope:

a2fe7c6 — links and the IBC partials

Your four link findings, plus three more of the same kind found by checking every external URL on the branch (283 of them):

File	Problem
interacting-with-cosmos/using-the-api.md	6 links, docs.cosmos.network moved its SDK docs under /sdk/
users/faucet.md	chains.tools no longer resolves (NXDOMAIN), entry removed
swap-with-squid-widget.md	rewritten, see below
operators/resources/snapshots.md	exrpd.tar.lz4 -> exrpd_latest.tar.lz4
operators/getting-started/installing-the-node.md	same dead S3 URL in its wget commands
operators/guides/upgrading-your-node.md	cosmovisor link, same /sdk/ move
interacting-with-cosmos/introduction.md	two more links, same move
operators/validators/join-the-proof-of-authority.md	governance explorer serves /proposals, not /xrp/proposals

The remaining sweep hits are false positives I deliberately left alone: 405 on JSON-RPC endpoints (POST only), 400 on WebSocket endpoints, 403 anti-bot from Medium/npm/Grafana, and placeholder URLs inside code snippets.

The Squid one was not a stale URL. The page documented a <script> tag and a SquidWidget.init() global that have never existed in any release of the widget, so the guide was unusable as written. Rewritten against the real @0xsquid/widget React component.

Also folded in the IBC table dedupe you asked for, on both the Mainnet and Testnet tabs.

7829d03 — frontmatter

blurb is not just invalid, it is inert: the live pages emit no <meta name="description"> at all and the blurb text appears nowhere in the rendered HTML. labels, html and status are dead the same way, so all four are gone across the 15 files that carried them — otherwise this PR fixes three files and leaves the identical dead keys in twelve others.

Each page now has a seo.description written against its own content rather than the old blurb, 141-151 chars and unique across the set, which gives the portal meta descriptions it has never had. Deviation from your suggestions noted in each thread.

One thing not fixed, flagged so it does not slip through

The Mainnet snapshot link no longer 404s, but the bucket holds a single 79 MB object last modified 2026-04-22. For a chain around block 7.37M that is not a usable snapshot — Testnet's is 9.9 GB. The row will look fine to a link checker and still fail an operator. Raised with the team that owns the bucket; if the job is not coming back I would rather drop the Peersyst row than ship it. Your call whether that belongs in this PR.

Left all nine threads open for you to resolve.