TL;DR Ethereum developers postponed Glamsterdam’s Hoodi activation after concerns emerged over how EIP-8037 could interact with existing smart contracts under new gas-accounting rules. The de
TL;DR
Ethereum developers postponed Glamsterdam’s Hoodi activation after concerns emerged over how EIP-8037 could interact with existing smart contracts under new gas-accounting rules.
The delay removes the October 26 Amsterdam and Gloas activations plus Hoodi’s planned 200 million gas limit increase, with no replacement date set.
Researchers identified compatibility risks for contracts relying on fixed gas assumptions, but no active exploit or Glamsterdam mainnet activation has been confirmed for the network.
Ethereum developers postponed the Glamsterdam upgrade on the Hoodi testnet after security concerns emerged around how EIP-8037 could interact with existing mainnet smart contracts. In an official update, the Ethereum Foundation removed the October 26 activation and left the replacement date open. The decision pauses Hoodi deployment while developers investigate contract behavior under the proposed gas-accounting rules. The issue affects testing for Ethereum, not the current mainnet protocol.
Glamsterdam changes how Ethereum prices state creation and access through EIP-8037 and EIP-8038. Security researchers found that some contracts relying on hardcoded gas limits, fixed stipends or assumptions about remaining gas could behave differently under the new accounting model. The concern is compatibility with a small subset of existing contracts, not evidence of an active exploit on Ethereum today. The risks were already part of warnings around Glamsterdam’s gas repricing before the Hoodi delay.
One issue involves contracts that catch failed calls and then continue executing. Under the proposed rules, gas charged for creating certain state can be restored when those changes revert, potentially leaving enough gas for failure-handling logic to complete when older assumptions expected the entire transaction to revert. Changing remaining-gas behavior can therefore alter outcomes in contracts built around previous execution assumptions. Researchers also identified the opposite possibility, where higher state-creation costs could cause operations with fixed gas budgets to fail.
The postponement removes the planned Amsterdam execution-layer activation, Gloas consensus-layer activation and Hoodi’s scheduled increase to a 200 million gas limit. It changes only the configuration for a future upgrade and does not revert Hoodi’s chain history. The 200 million gas test is postponed alongside Glamsterdam rather than independently abandoned. Ethereum had already tested that higher-capacity configuration on Sepolia, where Glamsterdam raised the testnet gas limit toward 200 million after its October 6 activation.
No replacement Hoodi epoch or timestamp has been announced. Node and validator operators must update client configurations that still schedule the old October 26 fork, while mainnet users and ETH holders need take no action. The delay does not establish a new mainnet timeline and does not mean existing contracts are currently being exploited through Glamsterdam’s proposed rules. Hoodi remains the next public testing stage after Glamsterdam’s Sepolia deployment, with developers now prioritizing compatibility analysis before rescheduling the upgrade for another test on Hoodi.
