fix(docs): update Arbitrum testnet chain ID from 421613 (Goerli) to 421614 (Sepolia) - #633
fix(docs): update Arbitrum testnet chain ID from 421613 (Goerli) to 421614 (Sepolia)#633Sertug17 wants to merge 2 commits into
Conversation
…21614 (Sepolia) Chain ID 421613 is the deprecated Arbitrum Goerli testnet which was shut down. The current Arbitrum testnet is Arbitrum Sepolia with chain ID 421614. Updated in three ethers.js code examples.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe Arbitrum documentation now uses chain ID ChangesArbitrum testnet documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
akegaviar
left a comment
akegaviar
left a comment
There was a problem hiding this comment.
Thanks — this one is a real bug and the diagnosis is exactly right. I verified it three ways before touching it: the ethereum-lists/chains registry has 421613 as Arbitrum Goerli and 421614 as Arbitrum Sepolia, the Chainstack platform only offers arbitrum-sepolia (there is no Goerli option left to deploy), and our own Networks table already lists the Arbitrum testnet as Arbitrum Sepolia. So the page really was telling people to configure a network that no longer exists. All three of your line changes are correct.
Requesting changes for one thing only: there is a fourth 421613 in the repo, and it is on a live page too.
reference/arbitrum-getting-started.mdx, line 16:
You can also try out Arbitrum on the Chainstack platform by deploying an Arbitrum Sepolia
testnet node and bridging some Sepolia ETH using the
[testnet Arbitrum bridge](https://bridge.arbitrum.io/?l2ChainId=421613).
The sentence says Sepolia twice and then links to Goerli. The mainnet bridge link two lines above it correctly uses 42161, so this one is just stale. Same fix — 421613 → 421614.
Could you add that to this PR? Then I will merge.
One thing so you do not duplicate effort: your report made me check whether the same pattern existed elsewhere, and it does — docs/optimism-tooling.mdx has Testnet: 420 (Optimism Goerli, now 11155420) and docs/polygon-tooling.mdx has Mumbai testnet: 80001 (Mumbai is shut down, Amoy is 80002), three occurrences each, same * Testnet: <id> shape you found. We are taking those two in a separate PR on our side, so please keep this one scoped to Arbitrum.
For what it is worth, that cross-protocol sweep only happened because you filed this. Good catch.
…ng pages (#634) Two live tooling pages handed out a chain ID for a testnet that no longer exists, so anyone copying one configured a provider against nothing. - optimism-tooling.mdx, three occurrences: 420 is Optimism Goerli. OP Sepolia is 11155420. - polygon-tooling.mdx, three occurrences: 80001 is Mumbai, which is shut down. Amoy is 80002. The label changes with the number, since it named the network. Each verified three ways: the ethereum-lists/chains registry, the Chainstack deploy catalog (which offers only optimism-sepolia and polygon-pos-amoy, so the old testnets were not deployable at all), and our own Networks table, which already listed Optimism Sepolia Testnet and Amoy Testnet. Neither page carried a deprecation notice, and neither mentioned the current testnet name anywhere. Found by sweeping all 58 tooling and getting-started pages for chain IDs that the registry maps to a retired testnet, excluding pages that carry a deprecation notice. The Goerli-era tutorials are deliberately historical and correctly flagged, so they are untouched. Nothing else turned up: the remaining goerli hits are changelog entries, platform-API network enums, and a redirect. Prompted by #632/#633 from Sertug17, who reported the identical bug on Arbitrum. That one is handled in his PR. Also adds a missing blank line before "Example to run the deployment script:" in polygon-tooling.mdx, which was making that sentence a lazy continuation of the preceding list item instead of its own paragraph.
|
Added the fix for reference/arbitrum-getting-started.mdx line 16 bridge link updated from l2ChainId=421613 to 421614. Ready for review. @akegaviar |
2 participants
What
docs/arbitrum-tooling.mdxhad the Arbitrum testnet chain ID set to421613in three ethers.js code examples.421613is the Arbitrum Goerli testnet which was shut down. The correct chain ID for the current Arbitrum Sepolia testnet is421614.Updated lines 285, 310, and 336.
Why
A developer copying this chain ID into their project would configure their provider to connect to a non existent network, silently failing or producing confusing errors.
Closes #632