The highly anticipated 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 have decided to hold off on the deployment to allow for deeper investigation into how EIP-8037 interacts with existing mainnet smart contracts. At this time, a new activation date has not yet been set.
This latest update completely supersedes the schedule and activation instructions that were previously outlined in the official Hoodi testnet announcement published on October 16, 2026. Developers, node operators, and ecosystem participants who had structured their testing timelines around the late-October date will now need to readjust their plans as the network configuration undergoes a revision.
What Has Changed?
The decision to delay the upgrade was reached during All Core Developers Execution (ACDE) call #248. Core development teams concluded that more time is required to carefully study the potential implications of EIP-8037. Specifically, engineers want to ensure that the proposal integrates smoothly and predictably with smart contracts currently operating on the mainnet, mitigating any unforeseen risks before pushing the changes live on a public testnet environment.
This postponement effectively removes the scheduled Amsterdam execution layer activation and the Gloas consensus layer activation from the immediate timeline. Furthermore, the delay rolls back a planned adjustment to the network’s parameters: the gas-limit schedule, which would have dynamically raised Hoodi’s gas limit to 200 million at the exact same epoch, has also been shelved for the time being.
It is important to note that this action merely rolls back the configuration settings designated for the upcoming upgrade; it does not in any way revert the historical ledger or transactions of the Hoodi chain. The October 26 activation date is completely off the table, and the updated network configuration currently lacks any replacement activation epoch or timestamp. Core developers have indicated that the rescheduling of the replacement upgrade will be formally discussed and announced at a later date once the evaluation of EIP-8037 is complete.
Hoodi Node and Validator Operators
Individuals and organizations operating a Hoodi node or a validator must take prompt action. Operators are strongly advised to check both their execution layer and consensus layer clients for updated instructions that reflect the postponed activation ahead of the original October 26 target. Any software installations or custom network configurations that still hardcode or schedule Glamsterdam at the former activation time must be manually updated to align with the revised Hoodi configuration parameters.
Furthermore, operators should exercise caution regarding earlier documentation. The client release tables provided in previous announcements should not be treated as confirmation that those specific versions incorporate the postponement. Instead, infrastructure runners must closely follow their respective client team’s official release notes and specific instructions tailored for the revised Hoodi schedule. In addition, validator operators should carefully review any specialized guidance concerning their validator client infrastructure and external builder setups to ensure total synchronization with the network’s current state.
Client Releases
As development teams work to adapt their software to the postponed timeline, new client releases incorporating the updated Hoodi activation parameters will be rolled out. Operators are instructed to update both their execution layer and consensus layer clients strictly to software versions whose official release notes explicitly confirm that the October 26 Glamsterdam activation on Hoodi has been removed or modified.
Because software updates are being distributed dynamically as teams finalize their builds, node operators should monitor official channels and maintain close coordination with their client maintainers. Consensus layer participants running validators must ensure that both their Beacon Nodes and corresponding Validator Clients are updated simultaneously to prevent any consensus misalignments. Similarly, builder and validator tooling guidance will be continuously updated as instructions are confirmed for the postponed activation, meaning operators who rely on external block-building infrastructure must stay closely aligned with their chosen tooling providers.
Application Developers and Mainnet Users
Application developers who were preparing their smart contracts and decentralized applications for a test run on Hoodi should immediately halt plans centered around an October 26 Glamsterdam activation. Because the upgrade configuration has been rolled back without an immediate replacement date, any testing environments relying on the previous timeline will fail to match the live network parameters. A revised Hoodi activation schedule will be formally announced through official channels once developers are confident in the stability and security of EIP-8037.
It is also vital to emphasize that this announcement applies strictly to the Hoodi testnet. This postponement does not establish a Glamsterdam mainnet activation date, and Ethereum mainnet users, developers, and ETH holders do not need to take any action or alter their operations as a result of this testnet scheduling change.
Ethereum & Smart Contracts
Ethereum & Smart Contracts
Ethereum & Smart Contracts
