Why Vitalik Buterin’s Bold Defense of EIP-8037 Could Make or Break Ethereum’s Future State Costs—And What Every Investor Must Know Now!

Why Vitalik Buterin’s Bold Defense of EIP-8037 Could Make or Break Ethereum’s Future State Costs—And What Every Investor Must Know Now!

Alright, here’s the deal: Ethereum’s about to pull the rug out from under some old assumptions with this new Glamsterdam proposal, and it’s got everybody talking — especially Vitalik Buterin himself, who’s now in the hot seat defending EIP-8037. Imagine having to pay way more just to store data on the blockchain — we’re talking about gas fees shooting through the roof for writing new info to Ethereum’s permanent state. Why? Because if you let that state balloon unchecked, you end up with a monstrous, unwieldy network running slower than molasses in January. But the plot twist? Some apps built on the shaky premise that today’s gas prices are set in stone may find themselves gasping for air, or worse, flat-out broken. It’s a brutal wakeup call for developers and ETH holders alike: adapt or risk obsolescence. The question is, will the community flex and evolve, or are we headed for a costly implosion? Dive into the guts of what this means, and why flexibility in gas pricing isn’t just clever—it’s survival. LEARN MORE

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.

Advertisement

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.

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.

Post Comment

WIN $500 OF SHOPPING!

    This will close in 0 seconds