Vitalik Buterin defends EIP-8037 as Ethereum weighs steeper state costs
Dado Ruvic 2
The Glamsterdam proposal would make storing data on Ethereum far more expensive to keep state growth in check, and some existing apps may not survive the change
Vitalik Buterin has stepped in to defend EIP-8037, an Ethereum proposal that would sharply raise the gas cost of writing new data to the network’s permanent state.
The goal is to stop Ethereum’s state from ballooning as gas limits rise. The catch is that the change may break existing applications that assumed today’s prices would last forever.
Ethereum co-founder Buterin’s message to developers was pointed. He argued that teams should not treat gas metrics as fixed, and he stressed the need for flexibility in how the network manages its execution capacity.
What EIP-8037 actually changes
Every Ethereum node has to store the network’s “state.” That is the live record of account balances, smart contract code, and contract storage.
EIP-8037 tries to price that long-term burden more honestly. It separates “state gas” from ordinary execution gas, so that computation and permanent storage stop being billed on the same meter.
The proposal introduces a fixed cost-per-state-byte, or CPSB, set at approximately 1,530 gas per byte. New account creation, new storage slots, and contract code deployment would all be charged under this framework.
The resulting price changes are not subtle. Deploying a 24 KiB contract would go from approximately 4.95 million gas to 37.8 million gas.
Creating a new cold storage slot would climb from 22,100 gas to 110,020 gas.
The crypto and markets news you actually need—every morning.
Daily. Free. Join 34,000+ readers across crypto, finance, and policy.
Why Ethereum thinks it needs this
The core numbers explain the urgency. Ethereum’s state currently grows by about 110 GiB each year.
Under a hypothetical 10x increase in the gas limit, and without EIP-8037, that annual growth could potentially reach approximately 1,100 GiB.
EIP-8037 is designed to let throughput rise while keeping state growth stabilized at around 60-120 GiB per year.
The proposal was drafted in October 2025 by Maria Silva, Ansgar Dietrichs, and Jochem Brouwer. It is slated for the Glamsterdam upgrade, where it sits alongside a companion proposal, EIP-8038.
The growing pains have already started
Work on the Glamsterdam testnet has run into delays after at least 13 contracts were identified with outdated gas assumptions.
Any contract that forwards a fixed amount of gas for a storage write, or that caps gas on a call, could fail once state operations get more expensive.
Buterin’s defense lands squarely on that point. If teams treat gas costs as permanent constants, every future repricing becomes a crisis. If they design with flexibility in mind, repricing becomes routine maintenance.
What this means for developers, users, and ETH holders
For developers, the immediate task is an audit. Any application that deploys contracts, creates accounts, or writes new storage slots should check its gas assumptions against the proposed numbers before Glamsterdam ships.
Projects that deploy large contracts or spin up many new accounts face the steepest adjustment. Factory contracts, wallet deployment flows, and apps that write lots of fresh storage could see their costs rise meaningfully under the new schedule.
The things to watch are concrete. Keep an eye on whether the Glamsterdam testnet clears its contract compatibility issues, whether the CPSB figure of approximately 1,530 gas per byte holds through further review, and how EIP-8038 interacts with the final design.
Disclosure: This article was edited by Vivian Nguyen. For more information on how we create and review content, see our Editorial Policy.

