Key Takeaways

• Buterin’s examples put new account creation at 197,900 gas, compared with 36,600 under the existing schedule.

• A separate state gas reservoir would accommodate large contract deployments beyond the execution gas cap.

• Applications with hardcoded gas limits could require fixes before the Glamsterdam upgrade.

Why Ethereum State Creation Would Cost More

“The goal of EIP-8037 is to decouple Ethereum’s scaling limits: enable a much higher amount of execution (which is easy to scale), but only a little bit more state size growth (which is hard to scale),” Buterin wrote in a document shared via X. The Ethereum co-founder added:

“This is the most practical way to enable short-term scaling and safety at the same time.”

State is the information the Ethereum network maintains about accounts, balances, and smart contracts. Expanding it raises storage requirements and synchronization times, adding burdens that faster transaction processing alone cannot eliminate.

Buterin estimates annual state growth at roughly 110 GiB. His illustrative scenario increases that to about 1,100 GiB if the gas limit rises tenfold alongside other upcoming Glamsterdam changes, without EIP-8037’s repricing.

“For about 10 years now, Ethereum has followed a simple rule: the gas cost of a resource should reflect the actual burden it imposes on the network,” the network co-founder wrote.

His examples raise a new storage slot’s total cost from 22,100 to 110,020 gas. Deploying a 24 KiB contract would require 37,801,488 gas, compared with 4,947,200. These are resource charges expressed in gas units; the fee paid also depends on the prevailing gas price.

The proposal would charge 183,600 state gas whenever an operation creates an account, including through an ETH transfer. That component is distinct from the combined execution and state totals in his examples.

A separate reservoir would pay state creation charges first, drawing on execution gas only after the reservoir runs out. State gas would sit outside the approximately 16.7 million per-transaction execution cap, preserving the ability to deploy large contracts.

Glamsterdam’s Compatibility Problem

“But this does not solve every problem,” Buterin acknowledged. He identified risks for bridges and applications with fixed gas allowances. In one OP stack bridge example, a hardcoded 40,000-gas limit could allow a malicious transaction without reservoir gas to force an operation to fail while still being recorded as completed.

“Either way, it still requires significant front-end dev work for an application to keep working,” he wrote.

Possible remedies include changing refund timing, adding another reservoir, or exempting older contracts under compensating penalties. Buterin warned that deeper changes could break other applications and delay scaling and quantum safety work. He said Glamsterdam had already been delayed and favored intensive collaboration with affected developers.

For builders seeking immutable contracts, his warning was direct: “Don’t assume gas schedules are set in stone.” He also acknowledged that this expectation had not been adequately communicated to newer developers. Buterin also wants developers to establish explicit lists of protocol features expected to change and those likely to be stable over the coming upgrades.

ETH’s Store-of-Value Argument Meets Application Stability

The defense follows Buterin’s Nov. 8 argument that the native token ethereum (ETH) should be valued primarily as a store of value. He supported retaining fee burning while questioning its importance as a valuation foundation, writing that “the value of ETH comes from elsewhere.”

That distinction matters: charging more for scarce storage serves a resource-management objective, while maximizing fee destruction serves a monetary valuation thesis. Higher gas requirements alone do not establish that ETH becomes more valuable.

The harder test is whether Ethereum can make protocol changes predictable enough for developers to trust applications built without upgrade controls. Protecting affordable node operation supports decentralization, but users also need confidence that their smart contracts will keep functioning. A credible stability argument must account for both kinds of reliability.