Ethereum co-founder Vitalik Buterin is defending EIP-8037, a proposal to increase gas charges for creating accounts, storage slots, and contract code. Buterin argues that Ethereum must constrain database growth to expand transaction capacity without making independent node operation prohibitively expensive.
Decoupling Scaling Limits
According to Buterin's written defense, the goal of EIP-8037 is to enable higher execution capacity while limiting state size growth. "This is the most practical way to enable short-term scaling and safety at the same time," he wrote.
State represents the information the Ethereum network maintains about accounts, balances, and smart contracts. Expanding state raises storage requirements and synchronization times for network participants, creating challenges that faster transaction processing alone cannot solve.
Buterin estimates current annual state growth at roughly 110 GiB. Without EIP-8037, a tenfold increase in the gas limit alongside other upcoming Glamsterdam changes could raise that to approximately 1,100 GiB annually.
Proposed Gas Cost Changes
Under the proposal, new account creation would cost 197,900 gas compared with 36,600 gas under existing rules. A new storage slot's total cost would increase from 22,100 to 110,020 gas. Deploying a 24 KiB contract would require 37,801,488 gas versus 4,947,200 currently.
A separate state gas reservoir would accommodate large contract deployments, sitting outside the approximately 16.7 million per-transaction execution cap. This structure would allow state creation charges to be paid independently from execution gas.
Buterin emphasized that "the gas cost of a resource should reflect the actual burden it imposes on the network," a principle Ethereum has followed for approximately ten years.
Developer Compatibility Challenges
Buterin acknowledged that EIP-8037 creates compatibility risks for applications with fixed gas allowances. He cited an example involving a bridge with a hardcoded 40,000-gas limit that could be forced to fail while still recording as completed.
Potential solutions include changing refund timing, adding another reservoir, or exempting older contracts under compensating penalties. However, Buterin warned that deeper changes could break other applications and delay scaling work.
He advised that developers should not assume gas schedules remain fixed and recommended that the protocol establish explicit lists of features expected to change versus those likely to remain stable across future upgrades.


