The Ethereum co-founder is defending EIP-8037, a Glamsterdam proposal that would sharply raise the cost of creating new state on the network

Mon 16 Nov 2026 · 03:16 EST · 3 min read

In Ethereum

Share

Ethereum wants to grow up. Vitalik Buterin wants to make sure it doesn’t grow out of its own hard drive.

The Ethereum co-founder warned that a tenfold increase in the network’s gas limit could push annual state growth to about 1,100 GiB, up from roughly 110 GiB today. His fix is EIP-8037, a proposal that would make creating new state on Ethereum considerably more expensive.

What EIP-8037 actually changes

On November 16, 2026, Buterin publicly defended EIP-8037, which is set to be implemented as part of Ethereum’s upcoming Glamsterdam upgrade. The proposal targets one specific category of activity: anything that permanently expands the network’s state.

Think of Ethereum’s state as the network’s permanent filing cabinet. It holds accounts, storage slots, and contract code, and every new entry adds weight that the network carries forward indefinitely.

Right now, the cost of adding to that cabinet is bundled in with regular execution gas, the fee for running computations. EIP-8037 would split the two apart.

Under the proposal, state-expanding operations would draw from a dedicated state-gas reservoir. That reservoir would sit alongside the existing execution gas cap of approximately 16.7 million per block, rather than eating into it.

The new price list

The proposed numbers are where developers will start paying attention.

  • New account creation: from 36,600 gas to 197,900 gas
  • New storage slot: from 22,100 gas to 110,020 gas
  • Deploying a 24 KiB contract: from approximately 4.95 million gas to approximately 37.8 million gas

That works out to more than five times the current cost for a new account and nearly five times for a fresh storage slot. Contract deployment takes the biggest jump, at more than seven times today’s figure.

The crypto and markets news you actually need—every morning.

Daily. Free. Join 34,000+ readers across crypto, finance, and policy.

We respect your privacy. Unsubscribe anytime.

The contract deployment number also explains why the reservoir design matters. A cost of approximately 37.8 million gas would not fit under a 16.7 million execution cap, so the separate state-gas reservoir allows large deployments to bypass that ceiling entirely.

Buterin’s core argument rests on the scaling math. If gas limits rise tenfold without any change to how state creation is priced, state growth could climb from about 110 GiB to about 1,100 GiB per year. He characterized that trajectory as untenable.

Cheaper paths around storage

Buterin did not frame higher prices as the only answer. He also pointed to longer-term designs that could reduce how much applications lean on persistent storage in the first place.

Among the alternatives he raised were Merkle-tree airdrops and UTXO or keyed-nonce designs. He suggested these could serve as cheaper long-term options.

A Merkle-tree airdrop, in simple terms, lets a project publish a single compact fingerprint of who is eligible, instead of writing every recipient directly into storage. Users then prove their eligibility when they claim.

Glamsterdam’s growing pains

EIP-8037 arrives in an upgrade that has already hit some turbulence. Glamsterdam has faced delays tied to security findings and ongoing compatibility reviews.

Those reviews have flagged at least 13 contracts that rely on hardcoded gas limits. When gas costs shift underneath a contract that assumes a fixed number, things can break in unpleasant ways.

One of the affected contracts is the OP Stack bridge, which carries a gas limit of 40,000. Given that new account creation alone would cost 197,900 gas under EIP-8037, the tension is not hard to spot.

Core developers are reportedly leaning toward supporting the affected applications through the transition rather than pushing the upgrade back further.

Disclosure: This article was edited by Vivian Nguyen. For more information on how we create and review content, see our Editorial Policy.