Glamsterdam on Hoodi Postponed

Introduction

The Ethereum Foundation has announced that the Glamsterdam network upgrade on the Hoodi testnet, originally slated for October 26, 2026 at 17:42:48 UTC, will not occur as planned. The postponement is intended to allow further investigation of how EIP‑8037 interacts with main‑net smart contracts. No replacement activation epoch has been provided yet.

---

What changed?

• Upgrade delayed: The scheduled activation of the Amsterdam execution layer and the Gloas consensus layer has been removed.
• Gas‑limit schedule cancelled: The planned increase of Hoodi’s gas limit to 200 M at the same epoch will not happen.
• No chain re‑org: The postponement rolls back the configuration for the upcoming upgrade but does not revert any existing chain history.
• Future timing TBD: A new activation date will be announced later, once the necessary investigations are complete.

---

Impact on node and validator operators

1. Check client versions – Both execution‑layer and consensus‑layer clients must be updated to releases that explicitly note the removal of the October 26 activation. Do not rely on the earlier client‑release tables; follow the release notes from your client team.
2. Update custom configurations – Any scripts, Docker images, or configuration files that still schedule Glamsterdam at the old epoch need to be edited to match the revised Hoodi configuration.
3. Validator tooling – Review instructions for your validator client, beacon node, and any external block‑building infrastructure. Builders should await updated guidance from their tooling providers.
4. Monitoring – Keep an eye on the Ethereum Foundation blog and the relevant client repositories for announcements of the next upgrade window and associated client releases.

---

Guidance for developers and main‑net users

• Testing plans: Do not schedule Hoodi‑based testing or demo deployments around the October 26 date. Wait for the new schedule before aligning any test‑net activities.
• Main‑net unaffected: This postponement only concerns the Hoodi testnet. Ethereum main‑net users, ETH holders, and dApp developers on main‑net do not need to take any action.
• Stay informed: Subscribe to the Ethereum Foundation newsletter or follow the official blog to receive updates on the revised activation timeline and related client releases.

---

Practical next steps

1. Verify client versions – Pull the latest releases for your execution (e.g., Besu 26.10.1, Erigon, go‑ethereum) and consensus (e.g., Grandine, Lighthouse, Lodestar v1.50.1) clients.
2. Adjust configuration files – Remove any references to the October 26 activation epoch.
3. Monitor official channels – Watch for the forthcoming announcement that will set a new activation epoch and provide updated client release links.
4. Communicate internally – If you manage a validator operation or a development team, circulate this information promptly to avoid accidental activation attempts.

By staying proactive and keeping client software up‑to‑date, operators can ensure a smooth transition when the Hoodi testnet upgrade is eventually rescheduled.