
Ethereum core developers postponed the Glamsterdam upgrade on Hoodi, previously set for 26 October, to investigate EIP-8037 interactions with mainnet contracts. No new date is set.
In brief
- Core developers postponed Glamsterdam on Hoodi, previously scheduled for 26 October 2026 at 17:42:48 UTC, to investigate how EIP-8037 interacts with mainnet smart contracts.
- No replacement activation epoch or timestamp has been set, and the announcement does not set a Glamsterdam mainnet date.
- Hoodi node and validator operators must update execution and consensus clients to releases that explicitly remove the October 26 activation.
What happened
Ethereum core developers postponed the Glamsterdam upgrade on the Hoodi testnet, which had been scheduled for 26 October 2026 at 17:42:48 UTC, epoch 132,352, according to the Ethereum Foundation.
The decision was taken at ACDE #248 to allow further investigation of how EIP-8037 interacts with mainnet smart contracts, the post says.
The delay removes both the Amsterdam execution layer activation and the Gloas consensus layer activation, along with a gas-limit schedule that would have raised Hoodi's gas limit to 200M at the same epoch.
The change rolls back configuration for a future upgrade rather than reverting Hoodi's chain history, and no replacement activation epoch or timestamp has been set.
Why it matters
Hoodi is the last public rehearsal before any mainnet rollout, so a postponed activation pushes back the point at which developers can test Glamsterdam code under realistic conditions.
The foundation said the announcement concerns Hoodi only and does not set a Glamsterdam mainnet activation date, and that mainnet users and Ether
ETH holders need take no action.
Operators face immediate work.
The foundation advised Hoodi node and validator operators to check both execution and consensus layer clients before October 26 and to update any software or custom configurations that still schedule Glamsterdam at the old time.
It also warned that client release tables in the earlier announcement should not be treated as confirmation of the postponement; operators should follow release notes that explicitly state the October 26 activation has been removed.
New releases listed in the post include Lighthouse v8.3.2, Prysm v7.3.1 and Teku 26.10.2 on the consensus side, and go-ethereum v1.17.10, Nethermind 2.2.1 and Reth v2.8.1 on the execution side.
Application developers were told not to plan Hoodi testing around an October 26 activation.
The foundation said a revised Hoodi schedule will be announced separately, and that builder and validator tooling guidance will be added as it is confirmed.
What to watch
The next signals are a replacement Hoodi activation epoch and timestamp, confirmation of which client releases incorporate the postponement, and any statement on a mainnet date.
Earlier scheduling had already left the mainnet timeline open: Ethereum set Glamsterdam for Sepolia on 6 October while the mainnet date remained undecided.