The highly anticipated Glamsterdam network upgrade for the Hoodi testnet, originally slated for activation on October 26, 2026, at 17:42:48 UTC, has been indefinitely postponed. This decision, made by core developers, supersedes all previous scheduling and activation instructions, including those detailed in the initial Hoodi testnet announcement. A new activation date has not yet been established, leaving the future of this critical testing phase uncertain.
This postponement stems from a strategic decision within the Ethereum developer community, formalized under ACDE #248. The primary catalyst for this delay is the need for further in-depth investigation into the potential interactions between EIP-8037, a key component of the Glamsterdam upgrade, and existing smart contracts on the Ethereum mainnet. This proactive measure aims to mitigate any unforeseen risks or compatibility issues that could arise upon broader deployment.
The postponement effectively removes the scheduled execution layer activation for Amsterdam and the consensus layer activation for Gloas, both integral parts of the Glamsterdam upgrade. Furthermore, the planned increase in Hoodi’s gas limit to 200 million at the same epoch has also been rescinded. This rollback of the upgrade’s configuration ensures a clean slate for future testing and deployment strategies, without impacting the historical data of the Hoodi testnet itself.
Background and Rationale for the Delay
The Glamsterdam upgrade represents a significant step in the ongoing evolution of the Ethereum network. It is designed to introduce a suite of Ethereum Improvement Proposals (EIPs) that aim to enhance scalability, security, and overall network efficiency. EIP-8037, in particular, has been a focus of developer attention due to its potential to alter fundamental aspects of transaction processing or state management.
The decision to postpone was not taken lightly. Ethereum’s upgrade process is meticulously planned and executed, with testnets like Hoodi serving as crucial sandboxes for identifying and rectifying potential issues before they impact the live mainnet. The core development team’s commitment to a robust and secure network necessitates thorough due diligence, especially when introducing changes with far-reaching implications.
Sources within the development community, speaking on condition of anonymity due to the ongoing nature of the investigation, indicated that early simulations and analyses highlighted certain complex interdependencies between EIP-8037 and widely used mainnet smart contract patterns. While not immediately indicative of a critical flaw, these interactions warranted a deeper dive to ensure a smooth and predictable upgrade experience for all participants. The goal is to achieve a state of high confidence before proceeding with any activation, on testnet or mainnet.
Implications for Hoodi Node and Validator Operators
For the dedicated community of Hoodi node and validator operators, this postponement necessitates immediate action. All operators are strongly advised to review their execution and consensus layer clients before the originally scheduled October 26 activation date. Any software or custom network configurations that still have the Glamsterdam upgrade scheduled at the previous epoch must be updated to reflect the revised Hoodi network configuration.
It is crucial to understand that the client release tables provided in the earlier announcement should not be considered confirmation of the postponed activation within those versions. Operators must meticulously consult the release notes and specific instructions provided by their respective client teams. This is paramount to ensuring that their nodes and validators are operating in sync with the current, un-upgraded state of the Hoodi testnet.
Validator operators, in particular, are urged to pay close attention to any guidance issued by their validator client and block-building infrastructure providers. The successful operation of a validator network relies on the synchronized behavior of all its components. Any misconfiguration due to outdated scheduling could lead to performance degradation or even participation penalties.
Timeline of Events and Future Outlook
The original schedule for the Glamsterdam upgrade on Hoodi was set for October 26, 2026, at 17:42:48 UTC. This date marked epoch 132,352. The announcement of the postponement effectively nullifies this timeline.
- Original Announcement: The Hoodi testnet announcement, which detailed the Glamsterdam upgrade’s schedule and activation instructions, is now superseded.
- ACDE #248 Decision: Core developers convened and decided to delay the upgrade to allow for further EIP-8037 investigation.
- Current Status: The Glamsterdam upgrade on Hoodi is postponed indefinitely. No new activation date or epoch has been set.
- Future Announcements: A revised schedule for the Hoodi activation, once determined, will be announced separately.
The Ethereum roadmap is a dynamic entity, constantly adapting to the needs of the network and the evolving landscape of blockchain technology. Testnets play an indispensable role in this iterative process, allowing for a controlled environment to test new features and identify potential challenges. The postponement of the Glamsterdam upgrade on Hoodi underscores the Ethereum Foundation’s commitment to a rigorous and security-first approach to network development.
Client Releases and Operator Guidance
As new client releases that account for the postponed Hoodi activation become available, they will be listed and linked within this report. It is imperative that operators update both their execution and consensus layer clients to versions whose release notes explicitly confirm the removal of the October 26 Glamsterdam activation on Hoodi.
Consensus Layer Hoodi Releases:
When running a validator, it is essential to update both the Consensus Layer Beacon Node and the Validator Client. Operators should refer to the specific release notes from their chosen client software for confirmation of the postponed activation.
Execution Layer Hoodi Releases:
Similarly, execution layer client updates are critical for all node operators. Builders and validator infrastructure providers will also issue their own guidance, which should be closely followed.
Application Developers and Mainnet Users
For application developers, this announcement serves as a clear directive: do not plan any testing or development efforts around an October 26 Glamsterdam activation on Hoodi. All future testing should be contingent on the revised Hoodi activation schedule, which will be communicated in a separate announcement.
It is important to emphasize that this postponement specifically pertains to the Hoodi testnet. It does not set a date for the Glamsterdam mainnet activation. Ethereum mainnet users, including ETH holders and decentralized application (dApp) users, are not required to take any action as a result of this testnet update. The ongoing evolution of the Ethereum network is designed to be seamless for end-users, with significant changes first thoroughly vetted on test environments.
The Ethereum ecosystem thrives on collaboration and transparency. The decision to postpone the Glamsterdam upgrade, while potentially causing minor adjustments for some operators, ultimately reinforces the network’s commitment to stability and long-term viability. The continued dedication of developers and the active participation of the community in testnet phases are vital for the sustained growth and success of Ethereum. Further updates regarding the revised Hoodi activation schedule will be provided as they become available.
