Ethereum Core Devs to Decide on Gas Repricing Amid Contract Breakage Risks
Summary: Developers meet Thursday to choose between keeping, fixing or dropping EIP-8037 and EIP-8038 for Glamsterdam. Up to 15,000 contracts face potential breakage, with a few hundred thousand dollars at risk.
Ethereum core developers are scheduled to decide on Thursday whether to retain, modify or remove two gas repricing proposals that threaten to break up to 15,000 deployed smart contracts. The decision will take place during the All Core Devs - Execution (ACDE) #249 call, which begins at 14:00 UTC and is set to last 90 minutes. The agenda prioritizes the upcoming Glamsterdam upgrade, where developers will weigh the technical benefits of increased block capacity against the stability of existing applications.
The proposals in question, EIP-8037 and EIP-8038, reprice the cost of creating and accessing data stored on the Ethereum network. These changes are designed to prepare the protocol for Glamsterdam, an upgrade that allows block sizes to expand from 60 million gas to as much as 200 million gas. By increasing the cost of state usage, the proposals aim to prevent unchecked growth in the amount of data each node must store. Vitalik Buterin supported EIP-8037 in a November 16 post on X, warning that without such measures, a tenfold increase in the gas limit would push annual state growth to approximately 1,100 GiB, compared to the current ~110 GiB.
However, the changes disrupt assumptions relied upon by certain smart contracts, particularly those using hardcoded gas limits or specific gas-reservation patterns for security. Marius van der Wijden, a developer at the Ethereum Foundation, estimated that between 10,000 and 15,000 of the roughly 90 million deployed contracts are exposed to these changes. Van der Wijden assessed that a few hundred thousand dollars in value are currently at risk. The foundation has stated that any final decision should wait until audit results are made public and reviewed by the community.
Security firms have quantified the scope of the issue during recent testing. ChainSecurity reported 152 findings, 76 of which overlapped with the Ethereum Foundation’s internal search, bringing the total number of identified compatibility issues to around 200. Most of these findings stem from simple price increases rather than the new state-gas reservoir mechanism introduced by EIP-8037. Separately, Dedaub conducted an impact study that flagged 70 medium- to high-risk findings across approximately 25,000 contracts with non-trivial gas patterns. This count included 22 contracts that the foundation had previously missed. While ChainSecurity noted that most issues can be easily mitigated, some require contract upgrades or redeployments.
Rahul Kothari, an Ethereum Foundation developer, is expected to present spec feedback and share updates from outreach efforts during the call. His team’s outreach uncovered three high-severity issues and at least 25 medium-severity ones, with most impacted teams already working on fixes. Specific vulnerabilities have been identified in popular protocols. Jango, a builder for Juicebox, ran simulations on the Sepolia testnet under Glamsterdam gas rules. The results revealed a gap where a caller could skip a payment to another contract if the gas limit was set between 182,000 and 294,000. Jango noted that live versions of Juicebox cannot be fixed in place.
Core developers now face three primary options: keep the specifications unchanged, implement an accounting fix to address the incompatibilities, or pull EIP-8037 from the Glamsterdam upgrade entirely. Some developers have raised concerns that rolling back the changes could delay Glamsterdam by four to six months, which would subsequently push back post-quantum work. The Hoodi testnet fork, intended as a precursor to the mainnet launch, remains on hold with no new activation date scheduled. In October, Cryptopolitan reported that ChainSecurity had initially flagged contracts relying on the gas behavior targeted by these EIPs, leading to the current postponement.