Scaling capacity vs contract stability
The Glamsterdam upgrade clearly improves scaling by increasing gas capacity from 60 million to 200 million per block, a 3.3x jump that developers say would sharply lower costs for most users while keeping state growth in check. Marius van der Wijden, an Ethereum Foundation developer, warned during a Nov. 16 core developer call that this upgrade could break up to 15,000 smart contracts. The issue was flagged late in the development process. The problem centers on EIP-8037 and EIP-8038, which aim to increase the gas limit per block.
| Metric | Current | Post-Upgrade |
|---|---|---|
| Gas per block | 60 million | 200 million |
| Capacity increase | 1x | 3.3x |
AI-assisted audits by ChainSecurity and Dedaub found about 200 contract classes that face issues, most of which relate to gas-cost increases. Van der Wijden noted that "multiple contracts were relying on invariants in the protocol that are modified by 8037 and 8038." He estimated the impact would affect 10,000 to 15,000 contracts, which is a fringe subset of Ethereum’s 90 million total, with impacted value in the low hundreds of thousands of dollars. Van der Wijden said he shares "a lot of blame" as the last remaining scaling lead still at the Ethereum Foundation because timelines slipped amid reorganizations and budget cuts.
Developer pushback and roadmap delays
While the scaling capacity is a clear benefit, I find the risk of breaking contracts a steep price for more gas. Jango, the Juicebox protocol builder, warned the change undermines "composability" and shakes developer confidence. A Uniswap developer argued that EIP-8037 "should definitely be reconsidered" because the changes break certain invariants that some smart contracts rely on. The Ethereum Foundation already delayed the Glamsterdam testnet fork because of these gas-related security flaws, and developers stressed Monday that no decision has been made. Removing the proposed changes would delay the Glamsterdam upgrade and the broader post-quantum roadmap by four to six months, a delay developers say the network cannot afford as quantum and AI threats loom. The core developer team has not reached a decision and will address the question during the execution-layer call this Thursday.
