Ethereum Postpones Glamsterdam on Hoodi, Stalling Its 200M Gas-Limit Test

Ethereum core developers postponed the Glamsterdam upgrade on the Hoodi testnet on October 22, pulling the October 26 activation, and its planned gas-limit raise to 200M, off the calendar.

The decision came at ACDE #248, the recurring call where Ethereum's execution-layer client developers make protocol calls, and it was announced on the Ethereum Foundation blog the same day. The stated reason is EIP-8037: developers want more time to investigate how the proposal, one of the components of Glamsterdam, interacts with smart contracts already deployed on Ethereum mainnet. The blog post said the update supersedes the schedule and activation instructions in the Hoodi testnet announcement."

The 200M gas test is gone for now

The postponement removes three things at once: the Amsterdam activation on the execution layer, the Gloas activation on the consensus layer, and the gas-limit schedule that would have lifted Hoodi's limit to 200M at the same epoch. That last piece was the point of the exercise. Hoodi, a testnet used to rehearse network upgrades before they reach mainnet, was set to run a gas-limit test of roughly 3.3 times the current limit ahead of Glamsterdam. With the activation postponed, the protocol's scaling validation slips with it, and the 200M target now has no date attached.

The mechanics of the rollback are narrow. The change rolls back Hoodi's configuration for a future upgrade; it does not revert the testnet's chain history. Client releases tagged for the old schedule, including Lodestar v1.50.1, Besu 26.10.1, Ethrex v30.0.1-rc.2 and Nethermind 2.2.1, remain as release tags for a plan that no longer stands.

What it means for the mainnet timeline

The announcement concerns Hoodi only. The Ethereum Foundation said it does not set a Glamsterdam mainnet activation date, and no action is required from Ethereum mainnet users or ETH holders as a result of this update." A mainnet fork at 200M gas was never scheduled, so nothing mainnet has moved; what has moved is the rehearsal that would have de-risked it. The earlier preview of the Glamsterdam upgrade on Hoodi ran through the ePBS design and the node upgrades the original October 26 date required.

The delay also lands amid an unresolved technical question. Two days before the postponement, a Lido engineer warned publicly of a staking deposit hijack risk at Glamsterdam, but the blog post cites only the EIP-8037 investigation, and no official statement connects the two events.

No new activation date for Glamsterdam on Hoodi has been set.

The post Ethereum Postpones Glamsterdam on Hoodi, Stalling Its 200M Gas-Limit Test appeared first on Techreport.