- Ethereum will shut down the Holesky testnet following the completion of the Fusaka fork.
- Developer teams should plan migrations of testing, CI pipelines and nodes to alternative test environments.
Ethereum will retire the Holesky testnet after the Fusaka fork completes. The shutdown follows a planned lifecycle and is intended to consolidate testing on newer environments.
Orderly wind-down of Holesky and migration to successor testnets
Holesky has served as a large-scale staging network for validator and staking workflows since its launch. It was designed to mirror mainnet conditions, with a high validator count and ample supply for stress testing. With Fusaka reaching completion on Holesky, the network is entering a wind-down phase.
Teams that still depend on Holesky are expected to finalise validator exits, archive relevant chain data and redeploy on successor networks that reflect current protocol assumptions. The aim is to reduce operational overhead, limit tooling fragmentation and concentrate client testing where upcoming upgrades will be exercised most actively.
Impact on developers and infrastructure
Engineering teams should map all dependencies that reference Holesky and update configurations to point to replacement endpoints. This includes environment variables in continuous-integration systems, RPC URLs in application back ends, faucet and funding scripts, and alerting rules that track slot and epoch health. Validator operators should schedule exits and decommission nodes in an orderly sequence to avoid gaps in monitoring and to maintain clean audit trails.
Application developers who run end-to-end test suites are encouraged to refresh test accounts, regenerate funded addresses and validate fee assumptions on the target network. Security teams should repeat baseline checks such as replay protections, chain-ID validation and allowlists for deployment keys. Client and tooling maintainers can use the transition to prune compatibility code, retire bespoke workarounds and align configuration defaults with the networks that will host future protocol work.
Service providers that expose shared endpoints should communicate deprecation milestones to users, publish replacement RPC details and monitor residual traffic to Holesky. Data teams may wish to snapshot final state, index outstanding blocks and preserve canonical references used in documentation. The closure of Holesky narrows the surface area for test infrastructure while keeping a clear path for protocol testing after Fusaka, with developer activity expected to continue on alternative testnets that more closely track forthcoming mainnet upgrades.
