Ethereum sets Glamsterdam's Hoodi testnet activation for Oct. 26 with 200M gas target
In brief
- Glamsterdam is scheduled to activate on the Hoodi testnet on Oct. 26, 2026, at 17:42:48 UTC.
- Hoodi test pairs block production and validation changes with a 200 million gas target.
- Hoodi operators must update both execution and consensus clients before activation.
- ETH holders and mainnet operators have no action to take; mainnet timing remains undecided.
What changes on Hoodi
Glamsterdam combines Amsterdam on the execution layer with Gloas on the consensus layer. Two pieces stand out. Enshrined proposer-builder separation moves the exchange between block proposers and builders into the protocol (giving validators more time to check execution), while block-level access lists record accessed accounts, storage and state changes so clients can do more work in parallel.
The 200 million gas figure is a target, not a hard cap. CryptoSlate described it as a planned budget for computational work per block, and the gas-limit schedule sets client defaults and recommendations while preserving operator preferences. The actual block limit adjusts gradually under existing rules.
It isn't an instantly enforced ceiling.
What operators need to do
All Hoodi operators must update their execution and consensus clients before activation. Validators have more on the list: they'll need to update both the beacon node and validator client, then review new duties, builder-tooling compatibility and gas-limit settings.
Client readiness is uneven. As of CryptoSlate's Oct. 17 check, Ethrex's listed Hoodi version was a release candidate, and Grandine, Lighthouse, Erigon, go-ethereum and Reth weren't yet listed among the Foundation's confirmed Hoodi releases. CryptoSlate advised operators to use releases whose notes confirm the Hoodi activation (so check each client's release notes directly before upgrading).
Besu users should read carefully. Besu 26.10.0 migrates Bonsai code storage on first startup and retains more history when pruning, and downgrading isn't simple: the documented besu storage revert-code-format command has to run before an older version can reopen the database.
Who doesn't need to act
ETH holders and mainnet operators have no action to take as a result of this Hoodi announcement.
There's no mainnet date to plan around yet. Smart contract developers do have homework, though. Changed gas pricing can affect contracts that rely on fixed stipends, hardcoded limits or remaining-gas assumptions, and the Foundation advises testing contracts and gas estimation under the new rules.
Frequently asked questions
Is the 200 million gas target an enforced block limit on Hoodi?
No. The 200 million gas target is a planned budget for computational work per block. The gas-limit schedule sets client defaults and recommendations while preserving operator preferences, and the actual block limit adjusts gradually under existing rules, so it isn't an instantly enforced ceiling.
Do ETH holders need to do anything about the Hoodi upgrade?
No. ETH holders and mainnet operators have no action to take because of the Hoodi announcement. Only Hoodi operators must update their execution and consensus clients before the Oct. 26 activation. The timing of Glamsterdam's mainnet activation hasn't been decided.
What does the Glamsterdam upgrade change?
Glamsterdam combines Amsterdam on the execution layer with Gloas on the consensus layer. Enshrined proposer-builder separation moves the proposer-builder exchange into the protocol and gives validators more time to check execution. Block-level access lists record accessed accounts, storage and state changes so clients can work in parallel.
