Skip to content

Remove Scroll Sepolia testnet content from the English docs - #562

Open
roylou wants to merge 1 commit into
prodfrom
remove-scroll-sepolia-prod
Open

Remove Scroll Sepolia testnet content from the English docs#562
roylou wants to merge 1 commit into
prodfrom
remove-scroll-sepolia-prod

Conversation

@roylou

@roylou roylou commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Description

Scroll Sepolia is being shut down, so this removes the testnet from the English documentation. Scoped to English on purpose — the es/tr/zh translations are being handled separately.

Changes

English content

  • developers/scroll-contracts — drop the whole "Scroll Sepolia Testnet" section (network info, contract addresses, predeploys, tokens)
  • developers/ (FAQ) — drop the Sepolia network parameters table, the Sepolia RPC provider list, the "Testnet ETH" section and the Sepolia node snapshot link
  • developers/faucetpage deleted; it was entirely about Scroll Sepolia testnet ETH. Its sidebar entry and the user-guide/faucet/en/developers/faucet redirect go with it, so the redirect doesn't start pointing at a 404
  • guides/bridge-erc20-through-the-custom-gateway and guides/scroll-messenger-cross-chain-interaction — these were written end-to-end against Sepolia. Rather than delete two complete tutorials, they are retargeted at Ethereum mainnet / Scroll Mainnet: contract addresses swapped for their mainnet counterparts, sepolia.etherscan.ioetherscan.io, and the bridge API example moved to mainnet-api-bridge-v2
  • l1-and-l2-bridging/the-scroll-messenger, transaction-fees-on-scroll, guides/running-a-scroll-node, guides/estimating-gas-and-tx-fees, ethereum-and-scroll-differences, technology/bridge/cross-domain-messaging, article-components — Sepolia endpoints, addresses and mentions removed or pointed at mainnet

Site config (single files, so these apply to every locale)

  • sidebar.ts — remove the "Sepolia Resources" section and the faucet entry
  • SearchModal.tsx — "Sepolia Testnet Contracts" search suggestion renamed
  • NetworkTabs.astro — deleted; it hardcoded a Sepolia/Mainnet tab pair and had no remaining usage
  • public/locales/en/translation.json — drop the now-unreferenced Sepolia keys

Left untouched

  • es/tr/zh translations — handled separately. Note that because the sidebar and redirects are shared across locales, those entries disappear for every language while the localized page content stays as-is
  • technology/overview/scroll-upgrades/* — the Sepolia mentions there record when each upgrade shipped to testnet, which stays true after the shutdown. One thing worth a follow-up: feynman-upgrade still carries operational Sepolia instructions (--scroll-sepolia flag, sepolia-sequencer-proxy.scroll.io, the Sepolia S3 blob endpoint) that will stop working
  • en/sdk/* — Sepolia there almost always means Ethereum Sepolia used as the L1 basechain for a self-hosted chain, which is unaffected. Three spots do refer to Scroll Sepolia and could be cleaned up later: sdk-faq ("defaults to the behavior seen on Scroll Sepolia"), production-deployment ("Scroll's Sepolia environment" resource table), and the "a public testnet like Scroll Sepolia" line in the AWS and DigitalOcean guides

Verification

astro build passes — 458 pages. No new Prettier violations (31 files in this set were already non-conforming on prod, unchanged after this).

Drive-by fix

guides/running-a-scroll-node had the mainnet and Sepolia S3 blob endpoints swapped in a comment (# scroll-mainnet : https://scroll-sepolia-blob-data...). Only the correct mainnet line remains.

Scroll Sepolia is being shut down, so remove the testnet from the
English documentation:

- drop the "Scroll Sepolia Testnet" section from the contract page
- drop the Sepolia network parameters, RPC providers, testnet ETH FAQ
  and node snapshot from the developer FAQ
- delete the Testnet ETH Faucet page along with its sidebar entry and
  the user-guide/faucet redirect that fed it
- retarget the custom gateway and ScrollMessenger guides at Ethereum
  mainnet / Scroll Mainnet (addresses, explorer links, bridge API)
- point the Scroll Messenger, transaction fee and node guides at the
  mainnet endpoints only
- remove the "Sepolia Resources" sidebar section, its English
  translation keys, the Sepolia search suggestion and the unused
  NetworkTabs component

Left untouched:

- the es/tr/zh translations, which are handled separately
- historical release notes under technology/overview/scroll-upgrades,
  whose Sepolia mentions record when each upgrade shipped
- the Scroll SDK docs, where Sepolia almost always means Ethereum
  Sepolia used as the L1 basechain, which is unaffected by this

Note that sidebar.ts, the search suggestions and redirects.json are
shared across locales, so those entries go for every language.
@vercel

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
scroll-documentation Ready Ready Preview, Comment Jul 29, 2026 2:06pm

Request Review

Comment on lines -221 to +219
The upgrade is expected to be finalized on February 21, 2024, after a two-week timelock. Scroll Sepolia has already undergone this upgrade. Read more [here](https://scroll.io/blog/protocol-upgrade-bridging-cost-reduction).
The upgrade is expected to be finalized on February 21, 2024, after a two-week timelock. Read more [here](https://scroll.io/blog/protocol-upgrade-bridging-cost-reduction).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need to rewrite history, I'd undo this and similar changes.


---

## Scroll Sepolia Testnet

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd keep contract addresses, chain id, etc. for historical reference. Just mark it somehow as deprecated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants