This sudden scheduling update supersedes all prior timelines, activation steps, and configuration guidelines previously outlined in the official Hoodi testnet announcement. The decision to hit the brakes on the upgrade comes as a precautionary measure to allow the development community more time to thoroughly evaluate technical elements and potential risks.
What Has Changed?
The decision to delay the rollout was reached during All Core Developers Execution (ACDE) meeting #248. Core developers agreed that pushing back the Glamsterdam network upgrade on the Hoodi testnet is necessary to allow for a deeper, more comprehensive investigation into how EIP-8037 interacts with existing mainnet smart contracts. Ensuring compatibility and security across complex smart contract environments remains a top priority for the network’s engineering teams before any major protocol changes are integrated.
With this postponement, several significant network modifications originally tied to the event have been temporarily removed from the immediate roadmap. This includes the scheduled Amsterdam execution layer activation, the Gloas consensus layer activation, and a planned gas-limit schedule that would have elevated Hoodi’s gas limit to 200 million at the target epoch.
Crucially, this modification rolls back the configuration settings for the upcoming upgrade rather than altering the historical record of the chain. Hoodi’s past transactions and chain history remain entirely intact and unaffected. The October 26 activation is no longer active in the network parameters, and the updated configuration currently lacks a replacement activation epoch or timestamp. Core developers indicated that a new schedule and replacement upgrade timeline will be formally announced at a later date once investigations into EIP-8037 conclude.
Hoodi Node and Validator Operators
Node and validator operators managing infrastructure on the Hoodi testnet must take prompt action to align their systems with the postponed activation timeline. Anyone running a Hoodi node or validator is strongly advised to review both their execution layer and consensus layer clients to ensure their software configurations reflect the delay ahead of the original October 26 target.
Any custom network configurations or software setups that continue to schedule the Glamsterdam upgrade for the original timestamp must be updated to match the revised Hoodi parameters. Operators are explicitly cautioned against treating the client release tables from the previous announcement as confirmation that those software versions automatically incorporate the postponement. Instead, infrastructure managers should closely monitor official client team release notes and adhere strictly to updated instructions for the revised Hoodi schedule. Furthermore, validator operators utilizing external builder infrastructure should carefully review any updated operational guidance provided by their validator clients and builder tooling providers.
Client Releases
As part of the adjustment process, new client releases that properly incorporate the postponed Hoodi activation are expected to be rolled out by various client development teams. Node operators must update both their execution layer and consensus layer clients exclusively to software versions whose official release notes explicitly confirm that the October 26 Glamsterdam activation on Hoodi has been removed from the configuration.
For validator operators running consensus layer infrastructure, standard operating procedures dictate that both the consensus layer beacon node and the validator client must be kept in sync and updated simultaneously. Similarly, execution layer clients must also be updated to ensure seamless compatibility with the network’s current state.
Builder and validator tooling guidance will be continuously updated and published as new information is confirmed regarding the postponed Hoodi activation. Operators relying on external block-building infrastructure should maintain close contact with their tooling providers and follow their specialized operational instructions during this transition period.
Application Developers and Mainnet Users
Application developers who have been utilizing the Hoodi testnet for pre-deployment testing must adjust their timelines accordingly. Testing routines should no longer be planned around an October 26 Glamsterdam activation, as a revised rollout schedule will be communicated through official channels at a future date.
It is important for the broader community to note that this announcement pertains strictly to the Hoodi testnet. This update does not establish a Glamsterdam mainnet activation date, and consequently, no action is required from Ethereum mainnet users, decentralized application teams, or individual ETH holders as a result of this latest development cycle.

Comments (0)