0x73c0f5a373c0…73c0f5a6

ConfirmedInfrastructure746 vB71 sat/vB4 min decode

Glamsterdam gas repricing could break 15,000 Ethereum contracts

Ethereum core developers weigh a four-to-six-month delay to Glamsterdam after research flagged up to 15,000 smart contracts at risk from the EIP-8037 gas repricing.

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

Outputs

  1. Up to 15,000 of roughly 90 million deployed Ethereum smart contracts could break under Glamsterdam gas repricing

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

  3. Block gas limit would rise from 60 million to about 200 million under the repricing

  4. ChainSecurity identified 152 specific contract compatibility issues

  5. Glamsterdam shipped on Sepolia on October 6, 2026; Hoodi activation paused, with core developers reconvening November 19, 2026

Up to 15,000 of Ethereum's roughly 90 million deployed smart contracts could break under the gas repricing in Glamsterdam, the network's next upgrade, per assessments by the Ethereum Foundation and security firms ChainSecurity and Dedaub cited on a core developer call Monday. No decision followed, and withdrawing the changes would delay the upgrade and Ethereum's post-quantum roadmap by four to six months.

What does the repricing actually change?

Two Ethereum Improvement Proposals carry the risk. EIP-8037 raises the cost of creating a contract from 32,000 gas to 183,600 gas, a 5.7-fold 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.

In plain terms: creating a contract becomes roughly six times more expensive, and reading or writing stored data gets repriced alongside it.

State is the permanent record of balances, contract code and stored data that every node must keep. The payoff developers cite is larger blocks. The repricing is tied to raising the block gas limit from 60 million to about 200 million, more than three times current capacity, which developers say would sharply lower costs for most users while keeping state growth in check.

Why some contracts cannot adapt

Contracts written on the assumption that gas costs would never move sit most exposed, according to the research. Automated systems and decentralized finance protocols that hardcode fixed gas amounts carry the most risk. When an operation suddenly costs several times more, a call with a fixed gas budget can simply fail, and contract code is often immutable, so teams may have no way to patch the assumption after deployment.

ChainSecurity separately identified 152 specific contract compatibility issues. The broader 15,000 figure is an upper-bound estimate, not a confirmed count of broken contracts, a distinction that matters to anyone sizing operational exposure.

Marius van der Wijden of the Ethereum Foundation said the potential financial impact of these vulnerabilities "could reach several hundred thousand dollars." Measured against roughly 90 million deployed contracts, the affected set amounts to about one in every 6,000, though it concentrates in the protocols that hardcode gas.

The takeaway is straightforward: the headline number is a ceiling, not a tally of failures.

Where does the rollout stand?

Glamsterdam is not hypothetical. It went live on the Sepolia testnet on October 6, 2026, at epoch 353,024. The next step, activation on the Hoodi testnet, has been postponed indefinitely while developers sort out the compatibility questions. Core developers reconvene on November 19, 2026, to revisit the upgrade's specifications, and that meeting is the next real checkpoint on whether the gas changes stay, shrink or get pulled.

What else ships with the upgrade?

Slated to follow the Fusaka hard fork, Glamsterdam touches both the execution and consensus layers. Beyond gas repricing, it will 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 also ship with the upgrade, telling clients in advance which accounts and storage a block will touch so nodes process transactions more efficiently.

What does this mean for builders and users?

For decentralized finance 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. Core developers have asked projects to report contracts they believe will be affected, and they are exploring mitigation through new EIPs while continuing work on the post-quantum roadmap in parallel.

There is 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. The research findings note that traders may see short-term uncertainty from the delay to Hoodi and the open questions around the upgrade, without quantifying that effect.

What should readers watch before November 19?

  • How many affected contracts projects actually report.
  • Whether any mitigation proposal gains traction among core developers.
  • Whether Hoodi receives a new activation date or stays parked.

For now, the only verifiable measure of the risk is the count of contracts owners choose to report, and the shape of the upgrade will not be settled until core developers reconvene on November 19, 2026.

via Crypto Briefing (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,525 articles