Vitalik Backs Ethereum Gas Overhaul To Curb State Growth

8 min read
3 views
Nov 16, 2026

Vitalik just threw his weight behind a major Ethereum gas shake-up that could raise costs for new accounts and contracts. Developers are split, airdrop projects face new hurdles, and the Glamsterdam timeline hangs in the balance. What happens next could redefine how the network grows.

Financial market analysis from 16/11/2026. Market conditions may have changed since publication.

I’ve been watching Ethereum’s scaling debates for years, and every so often a proposal lands that forces everyone to stop and rethink the basics. This week it was Vitalik Buterin stepping forward to defend a gas overhaul that many developers find uncomfortable. The idea is simple on the surface yet far-reaching in practice: make permanent state creation more expensive so the network can keep growing without drowning under its own data. Whether you run a node, launch tokens, or just hold ETH, the conversation matters.

Why State Growth Suddenly Became The Central Problem

Ethereum’s success created a quiet crisis. Every new account, every fresh storage slot, every large contract adds permanent data that full nodes must carry forever. Buterin recently put a number on it: the chain currently adds roughly 110 GiB of state each year. In a world where gas limits could rise tenfold without new rules, that figure might balloon toward 1,100 GiB annually. Hardware does not scale that fast for ordinary operators. Affordable disks and bandwidth have limits, and those limits are already starting to show.

I’ve found that people often focus on transaction fees or block times while overlooking the slower, heavier problem of state. Compute can be parallelized. Bandwidth can be optimized. Permanent storage keeps accumulating. Researcher Toni Wahrstätter called state growth one of the biggest long-term challenges precisely because ordinary hardware cannot keep expanding storage capacity at the same pace the network would like. That observation feels accurate.

What EIP-8037 Actually Changes

The proposal known as EIP-8037 raises the gas cost of creating new state. New accounts, unused storage slots, and contract code deployments would all become more expensive. Ordinary execution of existing code stays largely untouched. The goal is to separate the price of permanence from the price of temporary computation.

Concrete numbers help. Creating an account would jump from around 36,600 gas to roughly 197,900. Opening a new storage slot would move from 22,100 to about 110,020. Deploying a 24 KiB contract could climb from 4.95 million gas to nearly 37.8 million. Those figures are not dollar amounts. They depend on the prevailing gas price. Still, the direction is clear: creating lasting data becomes deliberately heavier.

Buterin described the approach as the most practical way to enable short-term scaling and safety at the same time. I tend to agree that pure capacity increases without cost signals risk pushing the network into territory where only large operators can participate. Decentralization is not just a slogan. It requires keeping the cost of running a full node within reach of motivated individuals.

How Airdrops And Launchpads Could Adapt

One of the first practical questions that arose concerned airdrop-heavy projects and memecoin launchpads. These applications often create many new accounts or storage entries in short bursts. Buterin’s response was straightforward. Use Merkle trees. The issuer posts a single root on-chain. Each recipient supplies their own proof and pays the gas to claim. The bulk of the cost shifts from the project to the users who actually want the tokens.

It’s already been recommended for airdrops to use a merkle tree based approach: the issuer only posts the root, each user provides their branch and pays their own gas to claim.

Longer term he pointed toward UTXO-style designs and keyed nonces for storing balances. These structures carry restricted access rules that could allow many nodes to avoid holding the entire state. The expectation is that both approaches end up significantly cheaper than traditional storage slots. That shift would not happen overnight, yet the direction is interesting. Token distribution patterns that once felt efficient may start looking wasteful under the new cost structure.

In my view this is healthy pressure. Applications that spray state across the chain without necessity have enjoyed a free ride for a while. Pricing that ride more accurately forces better design. Some teams will complain. Others will innovate. The latter group usually wins over time.

The Gas Reservoir Idea And Its Limits

EIP-8037 also introduces the concept of a state-gas reservoir. Storage-related charges can be paid outside the normal execution-gas ceiling of roughly 16.7 million. Large contract deployments that would otherwise exceed the block limit become possible again. That part of the design is pragmatic. Deploying complex systems should not become impossible simply because the accounting changed.

Yet the reservoir does not magically solve every compatibility issue. Buterin himself noted an OP Stack bridge mechanism that hardcodes a 40,000-gas allowance. Certain operations could fail if a transaction does not reserve enough state gas. Fixed assumptions baked into existing contracts suddenly become liabilities. Wallet developers and RPC providers will need to update gas estimation logic. Without those updates, users could see transactions that quote too little gas and then revert.

ERC-4337 account abstraction faces related friction. A companion idea, EIP-8038, would raise costs for accessing or modifying existing state. Smart contract wallets that rely on current gas assumptions may need careful review. None of this is catastrophic on its own. It is simply the cost of evolving a live system that already holds enormous value and complexity.

Why The Glamsterdam Timeline Slipped

The discussion did not stay theoretical. Developers pulled a planned October 26 activation of the Glamsterdam upgrade from the Hoodi testnet schedule while they assessed contract risks. The Ethereum Foundation identified eight assumptions in existing contracts that might break under the new rules. By early November it had received four concrete reports involving deployed contracts and was working with the affected teams.

Competing fixes appeared quickly. One suggestion was to keep older gas rules for contracts that already exist. Another proposed separating the accounting of gas from the actual fees charged. Neither has been adopted yet. Buterin argued that simply starting with smaller increases would still break the OP Stack bridge’s fixed allowance. Grandfathering old contracts might work if paired with penalties that prevent developers from exploiting cheaper rules indefinitely. More sweeping remedies, he warned, risk delaying both scaling progress and preparations for quantum-resistant cryptography.

I’ve seen this pattern before. Every major Ethereum upgrade surfaces assumptions that were never meant to be permanent. The network’s strength has always been its ability to adjust without fracturing. Still, the process is messy. Application teams that treated the gas schedule as immutable now face the reality that it never was.

Practical Advice For Builders Right Now

Developers writing new immutable contracts should stop assuming the current gas schedule will last forever. That advice sounds obvious, yet it is easy to ignore when deadlines press. Designing with future cost changes in mind costs a little extra time today and can save painful migrations later.

Teams that rely on heavy state creation should experiment with Merkle-based distribution patterns immediately. Even if EIP-8037 is delayed or modified, the efficiency gains remain useful. Lower state footprint is simply good hygiene.

  • Review any hardcoded gas limits in bridges, wallets, or factory contracts
  • Update gas estimation logic in front-end and RPC layers
  • Test large deployments against the proposed higher costs
  • Consider whether UTXO-style or keyed-nonce patterns fit the application
  • Engage early with core developers if a critical contract looks vulnerable

None of these steps guarantee zero friction. They do reduce the chance of unpleasant surprises when the upgrade finally lands.

The Broader Trade-Off Between Growth And Accessibility

Every blockchain faces the same tension. Users want higher throughput and lower fees. Node operators want manageable hardware requirements. Protocol designers sit in the middle trying to satisfy both. Raising the cost of state creation is one lever among many. Stateless clients, state expiry, and better data availability layers are others. EIP-8037 does not claim to solve the entire problem. It aims to buy time and shape incentives while deeper solutions mature.

Some will argue the increases are too aggressive. Others will say they do not go far enough. Both views have merit. What matters is that the conversation is happening in the open, with concrete numbers and public reasoning. Closed-door decisions tend to produce worse outcomes.

Perhaps the most interesting aspect is how quickly application patterns can shift once relative costs change. Merkle airdrops already existed as a best practice. Higher state costs simply make the best practice the only sensible practice. Similar pressure may push more projects toward designs that keep less data on the base layer permanently.

Looking Ahead To The November 19 Discussion

Core developers plan to review audit findings and possible specification changes at an All Core Developers Execution meeting on November 19. No new Hoodi activation date has been set. That pause is deliberate. Rushing an upgrade that breaks significant contracts would damage trust more than a measured delay.

Buterin urged teams building on Ethereum to collaborate with application developers before the changes go live. That collaboration is already underway. The four reported contract issues are being examined. More may surface. The process feels slower than some would like, yet it is the responsible path.

In the longer view, Ethereum’s ability to adjust its economic parameters while remaining live is one of its distinguishing features. Bitcoin changes far more slowly. Newer chains sometimes change too quickly and lose reliability. Ethereum tries to occupy a middle ground: deliberate, public, and still capable of evolution. EIP-8037 is simply the latest test of that model.

What Ordinary Users Should Watch

If you simply hold ETH or use established applications, the immediate impact will likely feel modest. Most daily transactions do not create large amounts of new state. The bigger effects will appear for projects that deploy frequently or distribute tokens at scale. Over time, cleaner state growth should help keep node requirements reasonable, which supports the decentralization that ultimately protects the value of the network.

Gas prices themselves remain a market. Higher base costs for certain operations do not automatically translate into higher average fees. They change which operations are attractive. Clever developers will route around the expensive paths. That adaptation is already visible in the Merkle-tree recommendation.

I expect the next few months to bring more detailed analysis from application teams and node operators. Some of the current numbers may be refined. Alternative designs may gain support. The core insight is unlikely to disappear: unbounded state growth is not free, and someone has to pay for it eventually.


Ethereum has always balanced ambition with caution. The current gas discussion is another chapter in that long story. Raising the price of permanence is uncomfortable for some. Leaving state growth unchecked is riskier for everyone. Buterin’s defense of EIP-8037 makes the trade-off explicit. The network now has to decide how firmly it wants to enforce that trade-off and how carefully it manages the transition. The answer will shape the next phase of Ethereum’s growth more than most people realize.

For builders the message is clear. Design for change. Prefer patterns that minimize permanent state. Test early against higher costs. Engage with the process rather than waiting for a finished specification. For the rest of us the message is quieter but still important. Healthy networks occasionally make their users and developers a little uncomfortable in the short term so they can remain viable in the long term. This appears to be one of those moments.

The November 19 meeting will not end the conversation. It will simply set the next set of parameters. After that comes more testing, more feedback, and eventually a decision on whether Glamsterdam moves forward with the current design or a modified one. Whatever the outcome, the underlying pressure remains. State cannot grow forever without consequence. Pricing that growth more accurately is one of the few tools available today. Using that tool wisely is the hard part, and the part worth watching closely.

In the end the question is not whether Ethereum should scale. Almost everyone agrees it must. The question is whether the path chosen keeps the network accessible to the people who actually run the nodes. EIP-8037 is an attempt to answer that question with economics rather than pure hope. Time will tell if the numbers are right, but the direction feels necessary.

❝
Money, like emotions, is something you must control to keep your life on the right track.
— Natasha Munson
Author

Steven Soarez passionately shares his financial expertise to help everyone better understand and master investing. Contact us for collaboration opportunities or sponsored article inquiries.

Related Articles

?>