Ethereum developers eye Dec. 14 Glamsterdam test despite 200 ChainSecurity findings
In brief
- Core developers tentatively targeted the week of Dec. 14 for a Glamsterdam test on Hoodi.
- ChainSecurity logged 200 findings: three high, 30 medium, 167 low, none critical.
- 24 findings require smart contract upgrades or migrations; most require configuration changes.
- Mainnet timing: mid-January is the soonest workable window; late January or February called more realistic.
What Glamsterdam changes
Glamsterdam is built to expand Ethereum's capacity, potentially lifting the block gas limit from 60 million to 200 million. Research firm Ethlabs said that room would let apps operate directly on mainnet and ease congestion and fees during heavy demand.
The friction comes from EIP-8037 and EIP-8038, which introduce new gas pricing and accounting rules that could break assumptions built into existing contracts. Part of it is simple: some apps rely on fixed gas allowances (amounts that might not be enough under the proposed rules).
200 findings, none critical
ChainSecurity's assessment logged 200 compatibility findings from its own investigations and from work coordinated by the Ethereum Foundation. Three were rated high severity and 30 medium. The remaining 167 were low.
None was critical.
The assessment flagged possible disruptions to bridges, exchanges, wallets, staking platforms, governance systems and other infrastructure. Most findings can be fixed through configuration changes, but 24 need smart contract upgrades or migrations, and the possible fallout includes locked funds and reward-accounting errors. In Juicebox V6 simulations, some transactions were recorded as successful even though internal payments failed or were skipped.
A split over changing the spec
Participants on the Nov. 19 call broadly supported proceeding with the current specifications rather than making changes that could push the upgrade to April or May 2027. It wasn't unanimous. The Besu client team wanted to explore a targeted revision to EIP-8037 that would preserve existing contract behavior, while Ansgar Dietrichs and several other developers questioned whether a narrow fix would solve enough to justify more testing and delays. Marius van der Wijden warned that changing gas refund handling could disrupt contracts that depend on receiving refunds during execution.
Ethlabs said gas price changes are needed for the expansion but separated them from the accounting changes behind the unexpected behavior. It added that protocol developers still have to convince app developers the upgrade is safe.
The Ethereum Foundation and security researchers have contacted more than 50 affected companies. Rahul reported that high-impact projects had finished, or expected to finish, fixes by mid-December. Others reported schedules running to Jan. 10, which puts the soonest workable mainnet window at mid-January if the specs don't change. Developers also discussed late January or the start of February as a more realistic target.
Frequently asked questions
When could Glamsterdam go live on Ethereum mainnet?
Developers tentatively targeted the week of Dec. 14 for a Hoodi test. Some affected projects reported fix schedules running to Jan. 10, so mid-January is the soonest workable mainnet window if the specs stay unchanged. A late-January or start-of-February rollout was also discussed as more realistic. None of these dates has been confirmed.
What did ChainSecurity find about Glamsterdam's compatibility?
ChainSecurity identified 200 compatibility findings: three high severity, 30 medium and 167 low, with none rated critical. Most can be fixed through configuration changes, but 24 require smart contract upgrades or migrations. Possible consequences include interrupted operations, locked funds and reward-accounting errors.
Why could Glamsterdam break existing smart contracts?
EIP-8037 and EIP-8038 introduce new gas pricing and accounting rules that could invalidate assumptions built into existing contracts. Part of the problem is that some applications rely on fixed gas allowances, which might not be enough under the proposed rules.


