Vitalik Buterin Defends Ethereum EIP-8037 Amid Gas Repricing Concerns
Ethereum co-founder Vitalik Buterin has defended the proposed EIP-8037 upgrade, arguing that Ethereum needs to charge more for creating new blockchain data if it wants to scale without making the network less decentralized.
In a November 16 post, Buterin explained that simply increasing Ethereum’s gas limit could put additional pressure on node operators. He also acknowledged that the proposed changes may create problems for existing applications, particularly those that rely on fixed gas limits.
If EIP-8037 passes, higher data‑creation costs will push smaller nodes out, reshaping Ethereum’s decentralisation landscape.
Developers must redesign contracts to avoid hard‑coded gas limits, preventing failures once the new gas reservoir activates.
Core devs will decide whether additional fixes or new upgrades are needed before Glamsterdam’s rollout, influencing Ethereum’s scaling roadmap.
His comments come ahead of an All Core Devs – Testing (ACDT) meeting scheduled for November 16 at 14:00 UTC. Developers will discuss audit findings and investigate how EIP-8037 and EIP-8038 could affect deployed smart contracts.
Why Ethereum Needs Gas Repricing
Buterin’s main concern is Ethereum’s growing state size. While execution capacity can improve through better hardware and parallel processing, increasing blockchain storage creates a different challenge.
Ethereum’s state currently grows by around 110 GiB annually. According to Buterin’s estimates, a 10-fold increase in the gas limit, alongside other Glamsterdam upgrades, could push annual state growth to approximately 1,100 GiB. That would increase storage requirements and make it harder for smaller participants to run Ethereum nodes.
“Execution is fine. Calldata is almost fine,” Buterin wrote, identifying state growth as the biggest remaining obstacle to increasing network capacity. EIP-8037 addresses this by increasing the gas cost of creating new accounts, storage slots, and smart contract code.
Under the proposal, creating a new account would cost approximately 197,900 gas, compared with 36,600 currently. Creating a new storage slot would increase from 22,100 to around 110,020 gas. Deploying a 24 KiB contract would also become more expensive, rising from approximately 4.95 million to 37.8 million gas.
How the Gas Reservoir Works
To manage the higher costs, EIP-8037 introduces a separate gas reservoir for state creation. Transactions may tap into this extra reservoir to cover operations that add new data to the blockchain. Operations first draw from the reservoir gas, then from execution gas.
Its purpose is to facilitate the execution of large contract deployments and other operations that would surpass the per-transaction execution gas cap of 16.7 million in most Ethereum environments.
Buterin also noted EIP-8141, which would let transactions specify execution and state gas limits independently, but this is currently not part of the present implementation.
Existing Applications Face Compatibility Risks
The new restrictions could be a stumbling block for applications that are designed to operate within defined gas limits.
Buterin highlighted the OP Stack bridge mechanism, which uses a hardcoded gas limit of 40,000. Under the new pricing rules, certain operations could exceed that limit.
He cautioned that in a worst-case scenario, an attacker might send a transaction without the required gas reservoir in place, leading to an exited user’s exit operation failing, even though it gets recorded as complete by the protocol.
There are other issues around GAS opcode not representing total gas used by subcalls with reservoir gas enabled. May also break compatibility for ERC-4337 account abstraction transactions.
Ethereum had postponed the October 26 Glamsterdam Hoodi upgrade after ChainSecurity flagged smart contract risks linked to EIP-8037 and EIP-8038, identifying 13 potentially affected contracts.
EIP-8038 presents another challenge by increasing the cost of the SSTORE operation from 5,000 to 12,100 gas, without providing a separate reservoir option for state I/O.
Buterin proposed fix options such as modifying the rules for gas refunds or creating another deposit for state I/O, but cautioned that those changes may actually break other compatibility requirements, thus driving future scaling development farther away.
Developers Prepare to Review Audit Findings
The concerns have also reached Ethereum’s core developer discussions.
The November 16 ACDT meeting includes findings from security firms ChainSecurity and Dedaub, investigations by the Ethereum Foundation and feedback from application developers. The Ethereum Foundation’s update outlined the ongoing investigations and the need to review potential compatibility issues.
Juicebox developer Matthew Leising, known as mejango, has submitted proof-of-concept examples showing how Glamsterdam’s changes could affect the protocol’s guarantees.
He asked developers to clarify whether these issues fall within the Ethereum Foundation’s acceptable threshold for breaking changes, arguing that developers building immutable applications need confidence in the network’s long-term stability.
Ethereum developer Marius Van Der Wijden previously confirmed that no decision had been made on specification changes or a Hoodi testnet deployment. The upcoming meeting is intended to review findings and collect further feedback.
Buterin Calls for Clearer Rules
Beyond the current upgrade, Buterin said developers should not assume Ethereum’s gas mechanics will remain unchanged.
He acknowledged that core developers have understood the possibility of gas repricing for years, but this expectation may not have been communicated clearly to newer application developers.
He advised developers against hardcoding gas limits and also listed other Ethereum features that could change in future upgrades, including the state tree, block hashing, blob structure and consensus mechanisms.
Buterin wants core developers to establish clearer guidelines identifying which protocol features may change and which are unlikely to be modified.
For now, Ethereum developers are focusing on identifying affected applications and finding compatibility fixes before Glamsterdam goes live. Further discussions will help determine whether additional changes to EIP-8037 and EIP-8038 are needed.
Also Read: Ethlabs Proposes Making Ethereum Post-Quantum and Post-AI by 2027
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


