docs: retire dead testnet chain IDs on the Optimism and Polygon tooling pages - #634
Merged
Conversation
…ng pages Both pages hand out a chain ID for a network that no longer exists, so anyone copying it configures a provider against nothing. - optimism-tooling.mdx, three occurrences: 420 is Optimism Goerli. Optimism 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 before changing: the ethereum-lists/chains registry, the Chainstack deploy catalog (which offers only optimism-sepolia and polygon-pos-amoy — the old testnets are not deployable), and our own Networks table, which already lists Optimism Sepolia Testnet and Amoy Testnet. Neither page carries a deprecation notice, and neither mentioned the current testnet name anywhere before this change. Found by sweeping every tooling and getting-started page for chain IDs that the registry maps to a retired testnet. Arbitrum has the same bug and is covered by #633 from an external contributor, which is what prompted the sweep. Also adds a missing blank line before "Example to run the deployment script:" in polygon-tooling.mdx. Without it the sentence is a lazy continuation of the preceding list item rather than its own paragraph; the Optimism page already has the blank line, so this matches them up. Verified: mintlify broken-links clean, both pages render 200 under mintlify dev with the new IDs present and no trace of 420, 80001, or Mumbai.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Contributor
|
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 (2)
📝 WalkthroughSummary by CodeRabbit
WalkthroughUpdated Optimism and Polygon tooling documentation with current testnet network IDs for ethers.js HTTP, ethers.js WebSocket, and Brownie examples. ChangesTestnet tooling documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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
pushed a commit
that referenced
this pull request
Aug 7, 2026
…ia) (#633) 421613 is Arbitrum Goerli, which was shut down. Arbitrum Sepolia is 421614, so anyone copying the old value configured a provider against a network that does not exist. - docs/arbitrum-tooling.mdx, three occurrences in the ethers.js examples. - reference/arbitrum-getting-started.mdx, the testnet bridge link, which read ?l2ChainId=421613 inside a sentence that says "Arbitrum Sepolia testnet node and bridging some Sepolia ETH". The mainnet link above it is unchanged. Verified three ways: the ethereum-lists/chains registry maps 421613 to Arbitrum Goerli and 421614 to Arbitrum Sepolia; the Chainstack deploy catalog offers only arbitrum-sepolia, so the old testnet was not deployable; and protocols-networks already lists the Arbitrum testnet as Arbitrum Sepolia. Neither page carries a deprecation notice. No 421613 remains on any live page. The same bug on Optimism (420) and Polygon (80001) was found by the sweep this report prompted and fixed in #634. Reported and fixed by Sertug17. Closes #632.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two live tooling pages hand out a chain ID for a testnet that no longer exists. A developer copying either one configures a provider against a network that isn't there.
docs/optimism-tooling.mdx×342011155420(OP Sepolia)docs/polygon-tooling.mdx×38000180002(Amoy)On the Polygon page the label changes with the number, since it named the network:
Mumbai testnet: 80001→Amoy testnet: 80002.Verified three ways each
420= Optimism Goerli,11155420= OP Sepolia;80001= Mumbai,80002= Amoy.optimism-sepoliaandpolygon-pos-amoy— the old testnets are not deployable at all, so the docs named networks a reader could not have used even if they wanted to.Neither page carries a deprecation notice, and neither mentioned the current testnet name anywhere before this change — Amoy appeared zero times in
polygon-tooling.mdx, Sepolia zero times inoptimism-tooling.mdx.How these were found
Sertug17 reported the identical bug on Arbitrum (
421613, Arbitrum Goerli) in #632 / #633. That report is correct and is being handled in his PR. It prompted me to sweep all 58 tooling and getting-started pages for chain IDs that the registry maps to a retired testnet, which turned up these two. Pages that carry a deprecation notice were excluded — the Goerli-era tutorials are deliberately preserved as historical and are correctly flagged.The sweep found nothing else: the remaining
goerlihits in the repo are changelog entries (historical records), platform-API network enums inopenapi.json, and a redirect, none of which should change.One adjacent fix
polygon-tooling.mdxwas missing a blank line before "Example to run the deployment script:", which made that sentence a lazy continuation of the preceding list item instead of its own paragraph. The Optimism page already has the blank line. Since the change sits on the line directly above, it is fixed here.Local validation
mintlify broken-links— clean.mintlify dev— both pages return 200, render the new IDs, and contain no remaining420,80001, or "Mumbai".10,137) confirmed untouched.