Ethereum (ETH) developers have postponed the planned Glamsterdam network upgrade on the Hoodi testnet, canceling an activation that had been set for October 26, 2026, at 17:42:48 UTC (epoch 132,352). No replacement date has been announced.
The decision, reached during the All Core Devs Execution call #248, gives the community additional time to examine how certain gas-accounting changes interact with smart contracts already deployed on Ethereum mainnet.
The postponement removes the scheduled Amsterdam execution-layer activation and the corresponding Gloas consensus-layer activation from Hoodi’s configuration.
It also eliminates the planned increase of Hoodi’s gas limit to 200 million at the same epoch.
This is a configuration rollback only; the testnet’s existing chain history remains unchanged, and operators must ensure their clients no longer treat the original timestamp as an activation point.
The Ethereum Foundation has advised Hoodi node and validator operators to review both execution- and consensus-layer client release notes before October 26 and to update software that still references the prior schedule.
Application developers are likewise instructed not to plan testing around the canceled date.
The announcement does not establish any mainnet activation timeline, and ordinary mainnet users or ETH holders are not required to take action.
The delay follows security analysis focused on two proposals included in Glamsterdam: EIP-8037 and EIP-8038.
These changes alter how the network charges gas for creating and accessing state. EIP-8037 introduces a separate state-gas reservoir and raises the cost of writing new permanent data, while EIP-8038 reprices state-access operations.
Together, the modifications can cause previously failing call paths to complete successfully even when contract code is left untouched.
In practical terms, an operation that once reverted because of insufficient gas may now finish and record a permanent outcome.
This undermines a common defensive pattern in which contracts rely on reversion to keep an action retryable rather than finalized.
Security firm ChainSecurity published a detailed examination of these interactions on October 13 and later confirmed that it has identified 13 real-world examples of deployed smart contracts potentially affected by the gas changes.
The firm is coordinating responsible disclosure with the projects involved and has urged developers to review their own contracts promptly while the Ethereum Foundation assesses the broader scope of impact.
The concern centers on insufficient-gas-griefing scenarios: a caller can supply just enough gas for an outer failure-handling routine to succeed while leaving the intended operation incomplete, converting what should have been a recoverable failure into a lasting state change.
Glamsterdam had already activated successfully on the Sepolia testnet on October 6, and Hoodi was intended as the final major public rehearsal before a possible mainnet window later in the year.
The temporary pause allows further investigation of contract compatibility before any rescheduling occurs. Updated client releases that explicitly confirm removal of the October 26 activation are being listed as they become available.
