Smart-contract developers may need to check whether their code relies on protocol assumptions that two proposed changes to Ethereum’s Glamsterdam upgrade would alter. As reported on November 18, 2026, developers were weighing the scaling benefits of EIP-8037 and EIP-8038 against the risk of disrupting existing contracts. No decision had been made.
The proposals are designed to raise Ethereum’s block gas limit—a measure of how much computation a block can contain—from 60 million to as much as 200 million gas, roughly 3.3 times the current level. Developers said the changes could lower costs for most users while keeping growth in the network’s stored data in check. But Ethereum Foundation developer Marius van der Wijden said some contracts rely on protocol assumptions that the proposals would change.
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 proposals’ new mechanics. Van der Wijden gave a high-end estimate of 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 at the low hundreds of thousands of dollars. Those figures were estimates, not a count of confirmed failures.

Van der Wijden said the scaling team had wanted to conduct substantial public outreach, but timelines slipped amid Ethereum Foundation reorganizations and budget cuts. He said he shared “a lot of blame” as the last remaining scaling lead at the foundation.
Application developers questioned the trade-off. Juicebox builder Jango warned that changing the assumptions contracts rely on could undermine composability—the ability of applications to work together—and confidence in building immutable protocols. A Uniswap developer said EIP-8037 “should definitely be reconsidered.”
The Ethereum Foundation had already delayed Glamsterdam’s testnet fork over the gas-related security concerns. After a Monday core developer call, the issue was due to move to a Thursday execution-layer call. Some developers favored keeping the changes, arguing that removing them could delay Glamsterdam and the broader roadmap toward post-quantum security by four to six months. That was their projected consequence, not an announced schedule change.
