Ethereum Sets October 26 for Hoodi Scaling Test with 200 Million Gas Target
Ethereum has scheduled its Glamsterdam upgrade test on the Hoodi network for October 26, 2026, featuring a 200 million gas target.
Ethereum Sets October 26 for Hoodi Scaling Test with 200 Million Gas Target
Ethereum has scheduled its Glamsterdam upgrade test on the Hoodi network for October 26, 2026, featuring a 200 million gas target.
Ethereum Hoodi Test Overview
According to CryptoSlate, Ethereum's upcoming Glamsterdam upgrade is officially scheduled to deploy on the Hoodi test network on October 26, 2026, at 17:42:48 UTC. This deployment gives node operators a strict deadline to upgrade their software ahead of the activation.
The Ethereum Foundation announced the testnet timing on October 16, following the earlier activation of Glamsterdam on Sepolia on October 6. Meanwhile, mainnet timing remains undecided, and everyday ETH holders do not need to take any action regarding the announcement.
Client Requirements and Upgrades
All Hoodi operators must update their execution and consensus clients before the activation timestamp. Validators are specifically required to update both their beacon node and validator client, while carefully reviewing new duties, builder-tooling compatibility, and gas-limit settings.
According to Foundation releases checked on October 17, Ethrex's listed version is a release candidate. Other clients such as Grandine, Lighthouse, Erigon, go-ethereum, and Reth remain unlisted, meaning operators should verify that release notes confirm Hoodi activation support.
Gas Target and Glamsterdam Mechanics
The upcoming Ethereum Hoodi test pairs changes to block production and validation with a scheduled 200 million gas target. This target serves as a planned budget for computational work per block, though the actual block limit adjusts gradually under existing rules rather than acting as an instant ceiling.
Glamsterdam combines the Amsterdam execution layer upgrade with the Gloas consensus layer upgrade. Enshrined proposer-builder separation moves exchange processes directly into the protocol, giving validators more time to check execution while block-level access lists allow clients to perform parallel work.
About The Author
