CoinSearcher

On-chain methodology, source charts, protocol analysis and valuation research

Glamsterdam’s Scaling Trade-Off: Higher Gas Limits, Contract Compatibility Risk

As reported on November 18, 2026, Ethereum developers were weighing whether two proposed changes for the Glamsterdam upgrade could raise block capacity without breaking assumptions embedded in existing smart contracts. No decision had been made.

EIP-8037 and EIP-8038 were intended to support an increase from 60 million to as much as 200 million gas per block—roughly 3.3 times the existing level—while keeping state growth in check. Developers said the changes could lower costs for most users. But Ethereum Foundation developer Marius van der Wijden said some contracts rely on protocol invariants that the proposals would alter.

ChainSecurity and Dedaub presented findings from AI-assisted audits. Their combined search identified roughly 200 distinct classes of affected contracts, most associated with gas-cost increases rather than the new mechanics themselves. Van der Wijden put the highest estimate at 10,000 to 15,000 affected contracts out of roughly 90 million on Ethereum. He loosely estimated the value affected among contracts not yet committed to upgrading in the low hundreds of thousands of dollars. Those are estimates, not a confirmed count of broken applications or losses.

Developers disputed how to weigh that risk. Juicebox developer Jango warned that the change could undermine composability and confidence in immutable protocols; a Uniswap developer urged reconsideration of EIP-8037. Van der Wijden acknowledged that planned public outreach had slipped amid Ethereum Foundation reorganizations and budget cuts.

The Foundation had already delayed Glamsterdam’s testnet fork over the gas-related security concerns. Developers said the question would move to a Thursday execution-layer call. Some favored retaining the changes, arguing that removing them could delay Glamsterdam and the broader roadmap toward post-quantum security by four to six months. The compatibility risk and the cost of delay remained competing arguments, not settled outcomes.

Further reading