Up to 15,000 Ethereum Contracts at Risk From Glamsterdam Gas Changes

Ethereum's core developers ended a call on Monday without settling what to do about two proposals that could stop as many as 15,000 contracts from working. The programs at issue are a sliver of the roughly 90 million deployed on the network, and the money exposed is small, a few hundred thousand dollars by the estimate given on the call. What has grown is the count. Four weeks ago the same gas-repricing work was pulled off a test network over 13 audited examples. Developers meet again on Thursday.
What EIP-8037 and EIP-8038 change
Both proposals reprice gas, the fee that measures computing work on Ethereum. EIP-8037 would charge separately for creating new permanent state, meaning a deployed contract or a fresh storage entry, instead of folding that cost into ordinary execution gas. Deploying a contract would cost about 183,600 gas against 32,000 now, a pair both accounts of the call carry. CoinDesk puts a new storage slot at roughly 97,920 gas against 20,000, a figure the other account does not mention. EIP-8038 changes what reading and writing existing data costs. The increases exist to keep the state database every node has to hold from growing too fast as later updates pack more into each block. Crypto Briefing ties the repricing to raising the block gas limit from 60 million to about 200 million, which would make ordinary activity cheaper. CoinDesk does not carry that figure.
Why some contracts cannot adapt
The exposed contracts are the ones that hardcode a fixed gas allowance when calling another contract. Raise the price of the operation and the call fails. Many were written to be immutable, so there is no patch to apply. That has opened an argument about what immutability was ever worth: code that cannot be changed can still behave differently once the rules underneath it do.
The count keeps moving
Where the 15,000 figure comes from depends on which account is read. CoinDesk credits Marius van der Wijden of the Ethereum Foundation, who gave it on Monday's call from broad scans. Crypto Briefing credits assessments by the Foundation together with the security firms ChainSecurity and Dedaub. The two do not reconcile on that point. Both treat the number as an upper bound and not a count of contracts known to break. The audit work underneath it is narrower. ChainSecurity's Tanguy Rocher reported 152 findings, about half of them overlapping the Foundation's own research for a combined total near 200, on a summary of the call posted to the Ethereum Magicians forum. Dedaub examined some 25,000 contracts with unusual gas usage and flagged 70 medium- and high-risk issues, 22 of which the Foundation had missed. Those last figures come from CoinDesk alone. This desk reported in October that developers cancelled the Hoodi activation on 22 October after an auditor produced 13 real-world examples. Thirteen examples and 15,000 contracts measure different things, and nothing published this week reconciles the two into a trend.
Thursday could decide little
Hoodi, a public test network, stays on hold until the bugs are resolved, and Glamsterdam has no confirmed release date. Crypto Briefing says the upgrade went live on the Sepolia test network on 6 October at epoch 353,024; CoinDesk makes no mention of Sepolia, and we could not confirm the epoch elsewhere. Ansgar Dietrichs, a Foundation researcher who helped write the proposals, argued on the call that the upgrade should go ahead, while granting that core engineers had communicated poorly with outside developers. Others said dropping EIP-8037 would stop developers deploying larger contracts and weaken the security goal. Crypto Briefing alone puts the price of pulling the changes at four to six months of delay for Glamsterdam and for the post-quantum roadmap; it stands unverified. The next call is on 19 November, and nothing on the record commits anyone to a decision there either.
Read also: Ethereum Merges a Glamsterdam Deposit Fix It Closed a Week Ago