Newsroom
17 November, 2026 / News / AI / Tags: gas, buterin, storage, ethereum, eip

Ethereum co-founder defends EIP-8037 as a practical measure to expand transaction capacity while containing long-term data storage growth on the network
Ethereum co-founder Vitalik Buterin has publicly supported EIP-8037, a proposal that would increase gas charges for operations that create new permanent state on the blockchain. The change is intended for inclusion in the upcoming Glamsterdam upgrade and seeks to allow higher execution throughput without a proportional rise in the data burden placed on nodes.
Buterin described the approach as a way to separate the cost of permanent storage from ordinary transaction execution. In comments shared on November 16, he stated that expanding computational capacity is relatively straightforward, while controlling the growth of blockchain state presents a harder constraint.
Under the current draft of EIP-8037, creating a new account would cost 197,900 gas in Buterin’s illustrative examples, compared with 36,600 under existing rules. Opening a previously unused storage slot would rise from 22,100 to 110,020 gas. Deploying a 24 KiB smart contract would require approximately 37.8 million gas, up from about 4.95 million.
These figures represent resource charges measured in gas units. The actual fee paid in ether depends on the prevailing gas price at the time of the transaction. The proposal targets the creation of new state rather than routine operations between already-existing accounts or contracts.
Buterin estimated that Ethereum currently adds roughly 110 GiB of state each year. In a hypothetical scenario in which the gas limit increased tenfold without corresponding changes to state pricing, annual growth could approach 1,100 GiB. Such expansion would increase storage, synchronization, and operational demands on nodes that maintain a full copy of the chain.
The proposal introduces a separate state-gas reservoir. This mechanism allows storage-related charges to be paid outside the ordinary execution gas limit of approximately 16.7 million per block, preserving the ability to deploy large contracts even when total gas consumption exceeds that ceiling.
Buterin acknowledged that the changes could affect existing applications, particularly those that rely on hardcoded gas allowances or specific assumptions about refunds and call parameters. One example cited involves an OP Stack bridge mechanism that uses a fixed 40,000-gas allowance. Certain operations could fail if transactions do not reserve sufficient state gas, requiring updates to application software.
Wallet developers and RPC operators would need to adjust gas estimation logic. Without those updates, applications might underestimate required gas and submit transactions that fail. Related concerns also arise for ERC-4337 account abstraction under a companion proposal, EIP-8038, which would alter charges for accessing or modifying existing state.
These risks contributed to a delay in Glamsterdam testing. Developers removed a planned October 26 activation from the Hoodi testnet schedule while assessing contract risks. Security researchers identified eight categories of assumptions in deployed contracts that could break under the new accounting rules. The Ethereum Foundation has received multiple reports of affected systems and is reviewing them with the relevant teams.
Competing mitigation ideas have surfaced, including preserving older gas rules for previously deployed contracts or separating accounting systems. Buterin indicated that most core developers currently favor direct collaboration with application teams to resolve issues rather than adding further protocol complexity. He cautioned that grandfathering existing contracts would require carefully designed penalties to prevent exploitation of cheaper legacy rules.
The Ethereum Foundation has scheduled a discussion of audit findings and potential specification adjustments at an All Core Developers Execution meeting on November 19. No new Hoodi activation date has been set.
In response to questions about airdrop-heavy applications and token launchpads, Buterin recommended Merkle-tree distributions. Issuers would publish a single root hash, while recipients submit their own inclusion proofs and pay the gas needed to claim tokens. Looking further ahead, he suggested exploring UTXO-style designs and privacy-preserving keyed nonces as potentially cheaper alternatives to traditional storage slots for holding token balances. Restricted access patterns in those models could allow many nodes to avoid retaining the full state.
Buterin urged developers of immutable contracts to avoid assuming that Ethereum’s gas schedule will remain static. He also called on core developers to document protocol features that may change in future upgrades, reducing the chance of unexpected breakage.
Researcher Toni Wahrstätter has described state growth as one of Ethereum’s most persistent scaling challenges, noting that affordable hardware does not expand storage capacity indefinitely. He has supported examination of higher disk limits and partial-state node designs while acknowledging open questions around synchronization and RPC services.
EIP-8037 remains a proposal under active discussion. Its adoption would form part of a broader effort to raise Ethereum’s execution capacity substantially while keeping long-term state growth within manageable bounds for decentralized node operators.









