0x417848574178…4178485a

ConfirmedInfrastructure687 vB151 sat/vB3 min decode

Ethereum’s EIP-8037 Would Charge 1,530 Gas per State Byte

EIP-8037 would set a 1,530 gas-per-byte state charge, raising contract and storage costs as at least 13 contracts with outdated gas assumptions complicate Glamsterdam testnet work.

Vitalik Buterin defends EIP-8037 as Ethereum weighs steeper state costs
WitnessVitalik Buterin defends EIP-8037 as Ethereum weighs steeper state costsgeralt / pixabay

Outputs

  1. EIP-8037 proposes a fixed charge of approximately 1,530 gas per state byte.

  2. A 24 KiB contract deployment would rise from about 4.95 million to 37.8 million gas.

  3. Ethereum state grows about 110 GiB annually and could reach 1,100 GiB under a 10-fold gas-limit increase.

  4. Maria Silva, Ansgar Dietrichs and Jochem Brouwer drafted EIP-8037 in October 2025 for Glamsterdam.

  5. At least 13 contracts with outdated gas assumptions were identified during delayed Glamsterdam testnet work.

EIP-8037 would set a fixed cost-per-state-byte, or CPSB, of approximately 1,530 gas for data added to Ethereum’s permanent state, a change designed to restrain state growth as network gas limits rise.

The proposal was drafted in October 2025 by Maria Silva, Ansgar Dietrichs and Jochem Brouwer and is slated for the Glamsterdam upgrade alongside EIP-8038.

Ethereum co-founder Vitalik Buterin defended EIP-8037 in a message to developers, arguing that teams “should not treat gas metrics as fixed.” His position was that flexible design makes future repricing routine maintenance rather than a recurring crisis.

What does EIP-8037 change?

Every Ethereum node stores the network’s state, the live record of account balances, smart contract code and contract storage. EIP-8037 would separate “state gas” from ordinary execution gas, so computation and permanent storage no longer share one billing meter.

According to the proposal, the schedule would change three creation costs:

  • New accounts: The framework would apply the state charge to account creation.
  • New storage slots: Creating a cold storage slot would rise from 22,100 gas to 110,020 gas.
  • Contract code: Deploying a 24 KiB contract would rise from approximately 4.95 million gas to 37.8 million gas.

The separation gives developers a clearer cost distinction: execution-only operations stay under ordinary gas, while writes that enlarge persistent state carry the new charge. It also shifts part of the network’s expansion burden from execution capacity to code that permanently adds data.

Why does Ethereum need higher state costs?

The proposal puts Ethereum’s current state growth at about 110 GiB per year. Under a hypothetical 10-fold increase in the gas limit, annual growth could reach approximately 1,100 GiB without EIP-8037.

EIP-8037 is designed to let throughput rise while holding state growth to roughly 60–120 GiB per year. The trade-off is direct: the proposal raises charges for permanent writes so that higher execution capacity does not produce an equally unchecked increase in stored data.

That approach also changes how applications forecast persistent costs. Teams can price a storage expansion separately from computation, making the gas requirements of account creation, new slots and code deployment more visible before deployment.

What is blocking the Glamsterdam testnet?

Glamsterdam testnet work has run into delays after at least 13 contracts were identified with outdated gas assumptions. Contracts that forward a fixed amount of gas for a storage write, or cap gas on a call, could fail once state operations become more expensive.

That compatibility exposure is the practical reason behind Buterin’s position. Code that assumes today’s prices will remain fixed can break after repricing, while code designed around variable gas requirements can treat the change as routine maintenance.

The issue is broader than contracts with large bytecode. A fixed gas allowance can sit inside an otherwise ordinary application, including a wallet flow or factory contract, and become insufficient when the same operation starts writing more expensive state data.

What should developers audit?

For developers, the immediate task is an audit of every application that deploys contracts, creates accounts or writes new storage slots. Teams should compare those operations with the proposed gas figures before Glamsterdam ships.

Projects that deploy large contracts or spin up many new accounts face the steepest adjustment. Factory contracts, wallet deployment flows and applications that write substantial fresh storage could see meaningfully higher costs under the new schedule.

The operational impact therefore extends beyond contract size. Account-heavy launches and storage-intensive services would need to reassess gas budgets and any code that assumes a fixed allowance for a write or downstream call.

What determines the final design?

Three items will determine the final design: whether the Glamsterdam testnet clears the contract compatibility problems, whether further review retains the CPSB at approximately 1,530 gas per byte, and how EIP-8038 interacts with EIP-8037.

Before Glamsterdam ships, the key cost-structure test is whether the final package retains roughly 1,530 gas per byte, clears the contract compatibility backlog and resolves how EIP-8038 interacts with EIP-8037.

via Crypto Briefing (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,514 articles