Ethereum developers postpone Glamsterdam upgrade on Hoodi testnet with no date
Ethereum developers delayed the Glamsterdam upgrade on the Hoodi testnet that had been scheduled for October 26. No new activation date is set. The delay stems from ongoing review of EIP-8037 interactions with mainnet smart contracts. The change removes the previously configured Amsterdam execution-layer and Gloas consensus-layer activations on Hoodi and cancels the planned Hoodi gas limit increase to 200 million. The Ethereum Foundation directs Hoodi operators to follow updated execution and consensus-client releases and states that Ethereum mainnet users do not need to take action.
What the announcement establishes
Primary facts: developers require more investigation of EIP-8037 before proceeding on Hoodi; the Amsterdam and Gloas activations on Hoodi are withdrawn; the gas limit raise on Hoodi to 200 million is cancelled; mainnet remains unaffected; no replacement Hoodi epoch or mainnet timeline is provided; client teams will issue updated releases for operators.
Why this matters for markets
Testnets surface interactions that do not always appear in isolated simulations. A postponement can disrupt developer calendars yet reduces the risk of deploying changes with unresolved compatibility issues. This is a software release management decision rather than a mainnet rollback. Price impact is likely limited until a change demonstrably affects users, capital flows, or network activity.
Scope and limits
The cancellation applies to a future Hoodi activation, not past blocks. The foundation provides no mainnet date and no new Hoodi schedule. Performance claims require precise definitions: throughput, finality, responsiveness, cost, and fault tolerance are distinct and improvements in one dimension do not guarantee gains in others when downstream systems add confirmations.
Context
The Glamsterdam Hoodi delay reflects increasing emphasis on cross-client testnet coordination. Stakeholders have different success criteria: users prioritize clarity and predictable access; operators prioritize reliable controls and manageable costs; institutions prioritize accountability. Reading updates through these lenses helps separate completed features from planned changes and from measured adoption.
What to watch
Key signals: findings from the EIP-8037 investigation; updated client release tables; a revised activation schedule. The operational test follows proposals and release notes: consistent cross-client implementation, safe developer upgrades, and user reliability during activity spikes. Evidence should come from official implementation updates and measurable outcomes rather than assumptions of immediate adoption or price response.
Primary source: Ethereum Glamsterdam Hoodi postponement published 2026-10-22.
Authors credited by the source: NewsBTC Editorial Team
Published by Holder based on an external source.
