Ethereum pauses Hoodi fork pending review of eight constants in Glamsterdam upgrade
Key Facts
Ethereum development teams decided to delay the Glamsterdam upgrade hard-fork path on the Hoodi testnet until issues related to gas-fee changes are addressed, according to an Ethereum Foundation announcement on November 6. The foundation said the All Core Developers team decided not to activate the upgrade on Hoodi before resolving these issues. It urged contract developers and auditors to check whether their projects rely on any of eight constants that could change under proposals EIP-8037 and EIP-8038. It said ChainSecurity had identified a few projects that could be vulnerable to the changes, without implying that eight projects were affected or that a flaw had been exploited. The foundation published a repository explaining the constants and including examples and questions to help teams review their code. The announcement did not set an alternative date for Hoodi activation.
The review focuses on software assumptions about the amount or cost of available gas, whose effects could change when network operations are repriced. ChainSecurity explains that gas refunds and price changes could allow a smart contract’s failure-handling path to complete in a case where it previously reverted. This could change the behavior of some contracts that base their logic on the call’s result or on the gas remaining afterward. The review therefore includes checking failure paths, not just verifying that ordinary transactions execute successfully. The foundation said its review coverage includes ChainSecurity, Dedaub and an internal audit. But it said it cannot cover every project on Ethereum, or their onchain and offchain code, making it part of developers’ and auditors’ work to check each project’s reliance on those constants.
ChainSecurity’s examples show that the change also concerns how the cost of creating and accessing state is distributed. In the company’s example, creating a new storage slot requires 97,920 gas in state fees, while a new cold storage-slot write incurs an additional execution cost of 12,100 gas. EIP-8037 proposes raising the cost of state creation and accounting for it separately to keep pace with network data growth as gas limits rise. The proposal targets average state growth of 120 GiB a year at a reference block limit of 150M gas units. EIP-8038 aims to update state-access costs to reflect its growing size and slower access; it proposes raising the cost of a cold account access from 2,600 to 3,000 gas, an increase of 15%.
The changes are driven by concerns that raising the gas limit could accelerate network data growth and strain node performance. EIP-8037 compares raising the block limit from 30M to 60M gas units with an increase in average daily new state from 105 MiB to 326 MiB. The proposal says that continued state growth along this path at a 200M limit could lift the annual increase to 387 GiB, exceeding the 650 GiB threshold associated with declining node performance in less than a year, starting from an initial size of 390 GiB. State-operation gas prices were last adjusted in the Berlin upgrade in 2021, according to the foundation’s explanation in August. The foundation said the proposed pricing schedule is based on a performance target that supports an increase of about 3 times in baseline throughput, and that repricing paves the way for a higher gas limit later.
In an August review, the foundation replayed historical mainnet transactions using the proposed pricing schedule and found a small group of contracts relying on assumptions that change under the schedule. The foundation said the vast majority of smart contracts were unaffected, and many of the identified cases could be fixed by raising the gas limit. One flagged assumption was allocating a fixed gas allowance, such as 2,300 gas in Solidity’s transfer and send functions. Other cases include hardcoded gas values in calls and logic that branches based on remaining gas. These details matter because repricing could change the amount of gas available to complete a particular path, even when the contract’s purpose or inputs do not change. The foundation is asking developers to review these patterns as part of the constants check before the upgrade path resumes.
On October 22, the foundation postponed Glamsterdam’s Hoodi activation, which had been scheduled for October 26, 2026 at 17:42:48 UTC, and removed from the proposed schedule a plan to raise the testnet’s gas limit to 200M at activation. The November 6 announcement confirmed the hard-fork process would be delayed until the issues were resolved, without providing a new date. The delay does not set a date for Glamsterdam activation on mainnet, and the foundation said Ethereum mainnet users and ETH holders do not need to take action because of it. The foundation had said a revised Hoodi activation schedule would be announced separately. In the testing process, the foundation said in an earlier announcement that Glamsterdam was activated on the Sepolia testnet on October 6, but that does not change the suspension of the Hoodi path. It also said work on the Hegota upgrade is continuing in parallel and is not affected by the delay.