Glamsterdam Upgrade on Hoodi Postponed Indefinitely Following Core Developer Consensus

Core developers of the Ethereum ecosystem have officially announced the postponement of the highly anticipated Glamsterdam upgrade on the Hoodi testnet. Originally slated to go live on October 26, 2026, at precisely 17:42:48 UTC, corresponding to epoch 132,352, the network upgrade has been put on hold while engineers and researchers conduct further investigations. At this time, a new activation date has not been set by the development community.

This latest scheduling update completely supersedes the previous activation instructions and timelines outlined in the earlier Hoodi testnet announcement. Node operators, validators, application developers, and other participants in the Ethereum testing ecosystem will need to adjust their preparations and monitor upcoming communications for a rescheduled activation roadmap.

What Has Changed?

The decision to delay the rollout was reached during All Core Developers Execution (ACDE) call #248. Core developers concluded that additional time is necessary to thoroughly investigate the interactions of EIP-8037 with existing mainnet smart contracts. Ensuring compatibility and mitigating any potential edge cases before pushing network-wide upgrades remains a top priority for the development teams overseeing Ethereum’s evolution.

By halting the current rollout plan, developers have effectively removed the scheduled Amsterdam execution layer activation and the Gloas consensus layer activation from the immediate calendar. Furthermore, this postponement strips out the proposed gas-limit schedule that was set to dynamically raise Hoodi’s gas limit to 200 million at the exact same epoch.

Crucially, this modification rolls back the configuration settings meant for the future upgrade without altering or reverting the historical record of the Hoodi chain. The network continues to function normally based on its current operational parameters. Because the October 26 activation is no longer active, the configuration files no longer feature a replacement activation epoch or timestamp. The eventual rescheduling of the Glamsterdam upgrade for Hoodi will be communicated formally once core developers finalize a new timeline.

Hoodi Node and Validator Operators

Anyone operating a Hoodi node or validator must review both their execution and consensus layer client setups to ensure configurations reflect the postponed activation before the original October 26 target date arrives. Software deployments or custom network setups that still retain the Glamsterdam upgrade scheduled for the old timestamp must be updated manually to align with the revised Hoodi network configuration.

Operators should exercise caution and avoid treating the client release tables found in previous announcements as confirmation that those specific software versions incorporate the latest postponement. Instead, infrastructure runners must closely follow the specific release notes and instructions provided by their respective client teams regarding the updated Hoodi schedule. Additionally, validator operators need to carefully inspect any operational guidelines associated with their chosen validator clients and external builder infrastructure to prevent unexpected behaviors when the network reaches the original epoch without the upgrade parameters.

Client Releases

As client development teams finalize new software builds incorporating the postponed Hoodi activation, updated instructions and software packages will be distributed. Node and validator operators are advised to update both their execution and consensus layer clients exclusively to software releases whose official notes explicitly confirm that the October 26 Glamsterdam activation on Hoodi has been removed or disabled.

Because these updates are published dynamically as client teams complete their testing, infrastructure operators should routinely check official channels and reference resources to ensure they are running the appropriate software versions. When running a validator, operators are reminded that both the consensus layer beacon node and the validator client must be kept in strict synchronization.

Builder and validator tooling guidance will similarly be updated as the ecosystem adapts to the postponement. Operators who rely on external block-building infrastructure should coordinate directly with their tooling providers to verify that their relay setups and bidding software are properly synchronized with the revised testnet environment.

Application Developers and Mainnet Users

Application developers who have built testing routines around the upcoming Glamsterdam features on Hoodi will need to adjust their development cycles. Testing should no longer be planned around an October 26 activation window, and developers should watch for future announcements detailing when the upgrade will be rescheduled on the testnet.

It is important to note that this announcement applies strictly to the Hoodi testnet environment. The decision does not set or imply a Glamsterdam mainnet activation date, and no action of any kind is required from Ethereum mainnet users, smart contract deployers, or ETH holders as a direct result of this testnet delay.