Glamsterdam on Hoodi Postponed
The Ethereum Foundation reports that the Glamsterdam upgrade on the Hoodi testnet has been postponed with no new activation date set. The delay is to further study EIP‑8037 interactions with mainnet contracts.
Points clés
- Glamsterdam on Hoodi, originally set for Oct 26 2026, is now postponed indefinitely.
- The postponement removes both the execution‑layer and consensus‑layer activation steps.
- The planned gas‑limit increase to 200 M at epoch 132,352 will not occur.
- Node and validator operators must update client software to reflect the new configuration.
- No impact is expected for Ethereum mainnet users or ETH holders.
- Original activation epoch
- 132,352
- Planned gas‑limit increase
- 200M
- Original date
- Oct 26 2026
Upgrade postponement
The Ethereum Foundation’s latest notice concerns the Hoodi testnet’s scheduled Glamsterdam network upgrade. Initially slated for 17:42:48 UTC on October 26 2026 (epoch 132,352), the upgrade has been delayed indefinitely while developers investigate how EIP‑8037 may affect mainnet smart contracts.
Reason and scope
Core developers voted on ACDE #248 to pause the rollout, citing the need for deeper analysis of cross‑layer interactions. The decision removes the planned activation of the Amsterdam execution layer, the Gloas consensus layer, and the associated gas‑limit schedule that would have raised Hoodi’s limit to 200 M. Importantly, the change does not rewrite Hoodi’s chain history; it merely cancels the upcoming activation.
Operational impact
Operators of Hoodi nodes and validators are instructed to verify that both their execution‑layer and consensus‑layer clients reflect the postponed schedule before the original date. Any software or custom configurations still targeting the old epoch must be revised. The Foundation cautions that earlier client‑release tables do not guarantee inclusion of the postponement, so teams should follow release notes that explicitly confirm the removal of the Oct 26 activation.
Next steps and caveats
New client releases that incorporate the updated Hoodi schedule will be announced as they become available. Validator operators should also monitor guidance for builder and infrastructure tooling, especially if they rely on external block‑building services. The Foundation emphasizes that this announcement applies solely to the Hoodi testnet; it does not set a Glamsterdam activation date for Ethereum mainnet, and no action is required from regular ETH holders.
What this means for the community
For developers testing on Hoodi, the postponement introduces uncertainty around timing but ensures that any potential incompatibilities with EIP‑8037 are addressed before deployment. Stakeholders should stay tuned for future updates on the revised activation timeline and adjust their test plans accordingly.