Hoodi Upgrade Delay Puts Ethereum Storage Repricing at 120 GiB Annual Target on Hold
Key Facts
Ethereum developers postponed the Glamsterdam upgrade on the Hoodi testnet until potential issues in deployed contracts are addressed, keeping the proposal to reprice state creation under review. EIP-8037 targets average annual state growth of 120 GiB at a reference gas limit of 150M units, with the cost of state creation accounted for separately. The Ethereum Foundation said the decision to delay the upgrade path followed the discovery of projects that could be affected by assumptions being changed in EIP-8037 and EIP-8038. It added that the impact review could lead to changes to the specifications or a new upgrade date. No date has been set for Glamsterdam activation on Hoodi or mainnet.
The proposal links fees to the volume of persistent data an operation creates or accesses, according to the Glamsterdam roadmap. The accounting separation aims to make the cost of state creation visible independently from the cost of executing an operation, allowing larger applications to be deployed without being constrained by old transaction limits. One example of the repricing is an increase in the cost of creating a new storage slot to 97,920 gas, from 20,000 gas currently. The proposed increase reflects a move to charge operations a cost more closely aligned with the persistent data they add to the network. These figures remain part of a specification under review, while the upgrade path depends on addressing compatibility concerns.
The rationale for controlling state growth is based on the increase recorded by the specification after the gas limit was raised from 30M to 60M units: average new state added daily rose from about 105 MiB to about 326 MiB. The specification also said the state-specific database of a Geth node reached about 390 GiB in January 2026. In a scenario using a gas limit of 200M, state growth could reach about 387 GiB a year. The specification estimates that this path could exceed the 650 GiB threshold, at which nodes begin to experience performance degradation, in less than a year. The repricing links greater network capacity with management of the volume of data nodes must retain and process.
Replaying historical transactions on mainnet revealed a small group of contracts that could fail or see their performance deteriorate after the gas changes, according to the Ethereum Foundation. The Foundation said, "Most observed issues can be resolved by increasing the gas limit, and the vast majority of smart contracts are unaffected." Patterns identified by the Foundation include some contracts' reliance on a fixed 2,300 gas allowance in Solidity's transfer and send functions, or on fixed gas values in calls. Contracts whose logic changes according to the amount of gas remaining could also be affected. The Foundation urged application developers and validators to check their projects for reliance on assumptions that will change, and to contact it if they find their project is affected.
In an update published on November 9, the Foundation said it had received four reports identifying deployed contracts that could fail under the proposed changes in EIP-8037 and EIP-8038. Ethlabs recommended postponing the decision until the audit results are published and time is available to review them, emphasizing that the decision to proceed with Glamsterdam rests with All Core Devs. According to Ethlabs, the upgrade aims to raise the gas limit per block from 60M to 200M, or 3.33x, while repricing operations is a prerequisite for that expansion. In May, the Ethereum Foundation announced that it had finalized the EIP-8037 repricing figures and chosen a fixed price per state byte instead of variable pricing, with any future repricing to take place at upgrade boundaries. This means assessing the rules' impact on existing contracts comes before proceeding with testing on Hoodi.
Dedaub, ChainSecurity and the Ethereum Foundation are scheduled to present the review findings at an ACDT session on November 16, with open questions to be aired and application developers encouraged to participate. The ACDE meeting on November 19 will then discuss the findings and possible next steps. The Foundation said no decision had been predetermined for the meeting agenda. Possible steps include changing the specifications or setting a new upgrade date after the issues are resolved. Until then, the activation date for Glamsterdam on Hoodi and mainnet remains undetermined, while the impact of the change on deployed contracts continues to be reviewed.