0x6aa6da846aa6…6aa6da87

ConfirmedInfrastructure590 vB48 sat/vB3 min decode

Ethereum's Glamsterdam Upgrade Could Break Up to 15,000 Smart Contracts

Ethereum Foundation, ChainSecurity and Dedaub estimate up to 15,000 contracts face disruption from Glamsterdam's gas repricing, as the Hoodi testnet activation sits postponed indefinitely.

Ethereum’s Glamsterdam upgrade could disrupt 15,000 smart contracts
WitnessEthereum’s Glamsterdam upgrade could disrupt 15,000 smart contractsBoskampi / pixabay

Outputs

  1. EIP-8037 raises contract creation cost from 32,000 gas to 183,600 gas under Glamsterdam.

  2. Up to 15,000 of roughly 90 million deployed Ethereum contracts could be affected, per Ethereum Foundation, ChainSecurity and Dedaub estimates.

  3. Glamsterdam activated on the Sepolia testnet on October 6, 2026, at epoch 353,024; the Hoodi activation is postponed indefinitely.

  4. Core developers reconvene November 19, 2026, to revisit the upgrade's specifications.

  5. The block gas limit would rise from 60 million to roughly 200 million under the proposal.

Ethereum's planned Glamsterdam upgrade could disrupt as many as 15,000 smart contracts, according to assessments by the Ethereum Foundation and security firms ChainSecurity and Dedaub. The exposure stems from two gas-repricing proposals that raise the cost of core operations some contracts assumed would never change.

The numbers are stark. EIP-8037 raises the cost of creating a contract from 32,000 gas to 183,600 gas — nearly a sixfold increase — and adds separate accounting for new state entries. EIP-8038 reprices storage reads and writes, changing what it costs to look up or modify existing data on-chain.

The payoff, developers argue, is bigger blocks. The repricing is tied to raising Ethereum's block gas limit from 60 million to roughly 200 million, which they say would sharply lower costs for most users while keeping state growth in check.

Why can't some contracts adapt?

The problem is hardcoded assumptions. Automated systems and decentralized finance protocols that budget fixed gas amounts for operations are the most exposed, according to the research findings. If a contract allocates a set amount of gas and that operation suddenly costs several times more, the call simply fails. And because smart contracts are often immutable, there may be no way to patch the assumption after deployment.

The scale needs context. The 15,000 figure is an upper-bound estimate out of roughly 90 million smart contracts deployed on Ethereum — not a confirmed count of broken code. ChainSecurity separately identified 152 specific contract compatibility issues. Marius van der Wijden of the Ethereum Foundation has indicated the potential financial impact of these vulnerabilities could reach several hundred thousand dollars.

Developers are now asking projects to report contracts they believe will be affected. They are also exploring mitigation through new EIPs, while continuing work on the post-quantum roadmap in parallel.

Where does the upgrade stand?

Glamsterdam is not hypothetical. It went live on the Sepolia testnet on October 6, 2026, at epoch 353,024. The next step was the Hoodi testnet, but that activation has been postponed indefinitely while developers sort out the compatibility questions.

Core developers are scheduled to reconvene on November 19, 2026, to revisit the upgrade's specifications. That meeting is the next real checkpoint for whether the gas changes stay, shrink, or get pulled entirely.

Glamsterdam is slated to follow the Fusaka hard fork and touches both the execution and consensus layers. Beyond gas repricing, it is set to include:

  • Enshrined proposer-builder separation through EIP-7732, which formally splits the job of assembling a block from the job of proposing it.
  • Block-level access lists under EIP-7928, which tell clients in advance which accounts and storage a block will touch, helping nodes process transactions more efficiently.

What should builders do before November 19?

For DeFi protocols, the immediate task is an audit. Any team whose contracts rely on fixed gas assumptions has reason to check its code now, before the November 19 call narrows the options.

The research findings note traders may see short-term uncertainty from the Hoodi delay and the open questions around the upgrade.

There's also a cost question for application users. Higher prices for state creation could change the economics for apps that deploy many contracts or write heavily to storage — even as everyday transfers get cheaper under a larger gas limit.

Three things matter heading into November 19: how many affected contracts projects actually report, whether any mitigation proposal gains traction, and whether Hoodi gets a new activation date or stays parked.

via cryptonews.net (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