Ethereum postpones Glamsterdam’s Hoodi test over contract risk
Ethereum postponed Glamsterdam’s Oct. 26 Hoodi test to investigate EIP-8037’s effects on deployed contracts; no replacement date or mainnet schedule is set.
By Web3 Hub Newsroom2 min read
Ethereum core developers postponed Glamsterdam’s Hoodi test, scheduled for Oct. 26, to investigate how the upgrade’s gas changes could affect existing smart contracts. The Ethereum Foundation’s announcement says no new activation date has been set.
What contract behavior raised concern?
Security firm ChainSecurity says Glamsterdam’s EIP-8037 and EIP-8038 changes can alter the gas available after a contract call fails. In its technical analysis, ChainSecurity explains that a failure handler could complete where it previously ran out of gas and reverted, potentially turning a retryable failure into a permanent one.
The firm also says the revised costs could make some operations require more gas than older contracts budgeted for. These are risks under the proposed rules; the Foundation said developers delayed the Hoodi activation to investigate EIP-8037’s interactions with mainnet smart contracts.
What has been removed from Hoodi’s schedule?
The postponement removes both the Amsterdam execution-layer activation and the Gloas consensus-layer activation from the Oct. 26 schedule, according to the Foundation. It also cancels a planned increase in Hoodi’s gas limit to 200 million at that activation.
The change updates the schedule for a future upgrade and does not reverse Hoodi’s chain history. The Foundation says Hoodi node and validator operators should check their execution- and consensus-client instructions so their software no longer schedules the old activation.
When will Glamsterdam be tested again?
The Foundation has not announced a replacement Hoodi date, epoch or timestamp. Its notice says the revised schedule will be announced later; it also says the postponement does not set a mainnet activation date.
For now, the next milestone is a new Hoodi schedule from the Ethereum developers. The Foundation says mainnet users and ETH holders do not need to take action because of this update.
References
- Ethereum Foundation’s announcement — blog.ethereum.org
- technical analysis — chainsecurity.com