Ethereum Foundation Logs Four Contracts at Risk Under Glamsterdam

The Ethereum Foundation confirmed on Nov. 9 that it has received four reports of deployed smart contracts that could break under the gas-fee changes proposed for the Glamsterdam upgrade. The disclosure comes as core developers keep the entire upgrade on hold pending further review.

The affected contracts relate to two proposals: EIP-8037 and EIP-8038. Both would change how Ethereum charges gas for certain operations and stored data. Gas is the fee mechanism Ethereum uses to price computation and data storage on the network, so any change to its schedule alters the cost profile — and in some cases the behavior — of contracts already running in production.

The risk is not hypothetical. Developers called off a planned Oct. 26 launch on the Hoodi testnet after suspending the Glamsterdam process over concerns around eight gas invariants. Those invariants are the assumptions about gas costs that many deployed contracts implicitly rely on; breaking them can render live applications non-functional.

What does this change for application teams?

Greg Markou, a former Ethereum core developer, addressed that question directly on Nov. 11. Developers "bundle 30 EIPs into a giant hard fork," he said, and "one of them's gonna break." His point was structural: the larger the upgrade, the higher the probability that at least one change interacts badly with production code.

Markou also quantified the intake problem. He estimated that about 10 Ethereum Improvement Proposals now arrive each day, and he attributed the growth in volume to the spread of artificial intelligence tools that can draft proposals at scale. Ten proposals a day is roughly 3,600 per year — a volume that strains a review process built around careful, manual scrutiny of each change.

His recommendation to application teams was concrete: test deployed contracts against the coming fork and report any problems to the Foundation. The guidance echoes an earlier warning from Markou that testnets can miss failures in live applications, because testnet activity does not fully reproduce the behavior of contracts operating under real conditions and real value.

For teams running production contracts, the practical sequence is now clear:

• Audit your contracts against the EIP-8037 and EIP-8038 gas schedules.
• Test on the fork's devnet configurations rather than assuming Hoodi coverage is sufficient.
• Report breakage to the Ethereum Foundation so it feeds into the review record.

The review window ahead

The next scheduled checkpoint is Thursday, Nov. 19, when the Foundation hosts a call to discuss audit findings. No decision on Glamsterdam's fate has been set in advance, which means the upgrade remains in a holding pattern until that discussion produces a consensus among core developers.

The stakes of that call extend beyond this fork. If gas-invariant breakage is confirmed in deployed contracts, developers face a choice between delaying the efficiency gains of EIP-8037 and EIP-8038 or accepting a compatibility break for live applications. Either path sets a precedent for how Ethereum handles gas-schedule changes in an environment where proposal volume — accelerated by AI drafting tools — continues to climb.