The upcoming Glamsterdam network upgrade on the Hoodi testnet, which was previously slated to take place on October 26, 2026, at precisely 17:42:48 UTC during epoch 132,352, has been officially postponed. Core developers made the decision to delay the rollout to allow for further comprehensive investigation into how Ethereum Improvement Proposal (EIP) 8037 interacts with existing mainnet smart contracts. At this time, a new activation date and epoch have not yet been determined, and the previous schedule outlined in the initial Hoodi testnet announcement is no longer in effect.
What Has Changed?
The decision to hit the pause button on the Glamsterdam upgrade came out of All Core Developers Execution (ACDE) meeting #248. Developers reached a consensus that additional scrutiny is required to ensure that the changes introduced by EIP-8037 do not cause unforeseen friction or vulnerabilities when interacting with smart contracts currently active on the Ethereum mainnet.
This postponement effectively rolls back several major elements that were bundled into the upcoming testnet configuration. Specifically, the delay removes the scheduled Amsterdam execution layer activation alongside the Gloas consensus layer activation. Furthermore, it scraps the proposed gas-limit schedule that would have temporarily raised Hoodi’s gas limit to 200 million at the target epoch.
Despite these alterations to the future upgrade path, developers and operators should note that this configuration rollback does not revert Hoodi’s historical chain data or transaction history. The October 26 activation date has simply been wiped from the calendar, and the updated network configuration contains no placeholder timestamp or replacement epoch. Core developers have indicated that a new timeline and scheduling details for the replacement upgrade will be announced publicly once investigations into EIP-8037 are complete and stakeholders are confident in the stability of the code.
Hoodi Node and Validator Operators
For individuals and organizations operating a Hoodi node or validator, immediate action is required to review both execution and consensus layer client setups. Operators must verify that their software configurations and local network parameters reflect the postponed activation status well ahead of the originally targeted October 26 date. Any custom network configurations or local software builds that still hardcode the Glamsterdam upgrade at the previous activation time must be manually updated to align with the revised Hoodi network configuration.
Furthermore, operators are advised not to rely on older client release tables published in previous deployment announcements as confirmation that those software versions successfully incorporate the postponement. Instead, infrastructure runners must closely follow the specific release notes and documentation provided by their respective client teams to ensure their nodes are running the correct, updated Hoodi schedule. In addition to standard node software, validator operators running staking infrastructure should thoroughly examine any operational guidelines or update instructions provided by their validator client teams and external block-building infrastructure providers.
Client Releases
As client development teams work to incorporate the postponed Hoodi activation into their software, official releases will be distributed to the community. Node operators are instructed to update both their execution layer and consensus layer clients exclusively to software versions whose release notes explicitly confirm that the October 26 Glamsterdam activation on Hoodi has been formally removed.
When running a validator on Proof-of-Stake Ethereum networks, operators must ensure that both the consensus layer beacon node and the underlying validator client are updated in tandem to maintain network synchronization and avoid potential slashing risks or missed attestations. For those utilizing external block-building tooling or validator middleware, specific guidance will be provided by tooling developers as compatibility updates are confirmed. Operators relying on third-party builder infrastructure should remain in close contact with their service providers to ensure their setups conform to the latest network requirements.
Application Developers and Mainnet Users
Application developers who have been utilizing the Hoodi testnet for pre-deployment testing must adjust their timelines accordingly and should no longer plan their development cycles around an October 26 Glamsterdam activation. Because the testnet configuration is currently in flux, developers should await a newly published activation schedule before resuming upgrade-specific integration testing.
It is important to emphasize that this postponement announcement applies strictly to the Hoodi testnet environment. The decision does not establish a Glamsterdam mainnet activation date, nor does it impact the current operating parameters of the Ethereum mainnet. General users, decentralized application users, and ETH token holders are not required to take any action or modify their behavior as a result of this development update.
Comments (0)