Hoodi’s Glamsterdam upgrade is delayed: what changed
Ethereum withdrew Hoodi’s 26 October upgrade schedule. Here is what the delay affects, why EIP-8037 is under review and what operators need to check.
The 26 October activation was cancelled
Hoodi’s scheduled Glamsterdam activation was cancelled. On 22 October 2026, the Ethereum Foundation withdrew the activation planned for 26 October at 17:42:48 UTC, epoch 132,352. The associated plan to raise Hoodi’s gas limit to 200 million was withdrawn too.
No replacement date was announced.
This was a testnet scheduling change. Hoodi’s chain history was preserved. Mainnet users didn’t need to move their ETH or change anything because of this notice.
Why EIP-8037 needs more investigation
Core developers wanted more time to examine how EIP-8037 interacts with mainnet smart contracts. The proposal changes what Ethereum charges for creating persistent state, including new accounts, contract code and storage, whose records remain a burden for nodes long after the transaction that created them has finished.
EIP-8037 proposes separate accounting for execution work and state creation. That allows developers to consider higher throughput while charging more deliberately for database growth. The postponement gives them more time to investigate how those rules interact with existing mainnet contracts.
Where Hoodi fits
Ethereum runs independent networks for testing. Hoodi gives protocol developers somewhere to test upgrades and gives stakers a place to rehearse validator operations. Sepolia has a different emphasis: it is the recommended testnet for application development.
A testnet has its own balances and transaction history. Activity there doesn’t move mainnet ETH between accounts. That separation lets teams exercise software before relying on it on the production chain, although a test environment can never reproduce every contract interaction that exists on mainnet.
What Glamsterdam is trying to change
Glamsterdam combines Amsterdam on the execution layer with Gloas on the consensus layer. Its wider programme includes changes to block production and preparation for more parallel processing, alongside state pricing. Enshrined proposer-builder separation would make the handoff between a block proposer and a builder part of the protocol.
Those are substantial changes to how blocks are assembled and checked. A gas-limit target alone says little about whether the whole package is ready. The withdrawn Hoodi schedule should be read alongside that wider testing job, without turning a testnet delay into a claim about a mainnet launch date.
Read the replacement release notes
The postponement reached the client software as well as the calendar. Lighthouse v8.3.2 explicitly disabled the scheduled Gloas fork on Hoodi and superseded its earlier instructions. Geth v1.17.10 postponed the corresponding Amsterdam fork; its release notes said other networks were unaffected.
For a Hoodi operator, checking just one client misses half the configuration. The relevant execution, consensus and validator software needs a consistent schedule. Use the linked release notes to understand this specific cancellation, then check the project’s latest instructions before choosing software. An older announcement table can’t establish that a particular build contains a later scheduling correction.
About these stories
CS2 and crypto, with sources
Follow Counter-Strike updates, tournament moments and major crypto developments. Our articles link to original announcements and records so you can read the source behind the story.
A date for the event, a date for the article
Event dates show when the reported announcement or milestone happened. Each article separately shows its actual publication date. Historical features look back at the event rather than claiming to have been published at the time.
Images are credited on the article. Illustrative images are identified in the credit; they are not photographs of the reported event.