KEY POINTS
- A ChainSecurity assessment found 200 compatibility issues with Glamsterdam's gas changes, including three rated high severity and none critical.
- Developers tentatively aim to test on the Hoodi network in the week of Dec. 14, which could allow a mainnet launch as early as mid-January.
- A decision on the December test is expected on the Nov. 26 All Core Developers Consensus call.
Ethereum core developers are leaning toward keeping the current gas rules of the planned Glamsterdam upgrade, even though a security review found 200 issues that could affect existing smart contracts, CryptoSlate reported. The discussion took place during a core developers meeting on Nov. 19.
Participants showed broad support for moving ahead with the present specifications instead of making changes that could push the upgrade back to April or May 2027. They tentatively aimed at the week of Dec. 14 for testing on the Hoodi test network. That schedule could allow a mainnet activation as early as mid-January, but it is not confirmed.
Glamsterdam is meant to raise Ethereum's block gas limit from 60 million to 200 million, an increase of more than threefold. Ethlabs, a research firm, said the added room would let applications run more directly on the main network and ease congestion and fees during busy periods. Reaching that capacity requires new pricing and accounting for certain computing operations and data storage, set out in two proposals, EIP-8037 and EIP-8038.
A ChainSecurity assessment counted 200 compatibility findings: three high severity, 30 medium and 167 low, with none critical. They could affect bridges, exchanges, wallets, staking platforms and governance systems. Most can be fixed through configuration, but 24 need smart contract upgrades or migrations. Possible outcomes include interrupted operations, locked funds and mistakes in reward accounting.
Part of the problem is that some applications depend on fixed gas allowances, which may no longer cover the same work under the new rules. Simulations of Juicebox V6 showed some transactions marked as successful even though internal payments failed or were skipped. Ethlabs said gas price changes are necessary but separated them from accounting changes that caused unexpected behavior, and argued protocol developers must convince application developers that the upgrade is safe.
Developers remain split on whether altering the specification would help. The Besu client team proposed exploring a narrow revision to EIP-8037 to preserve current contract behavior. Ansgar Dietrichs and others doubted that such a change would solve enough problems to justify extra delay, and Marius van der Wijden warned that changing gas refund handling could break contracts that rely on those refunds during execution.
The Ethereum Foundation and security researchers have contacted more than 50 affected companies. Rahul told the meeting that high-impact projects had finished or were expected to finish fixes by mid-December, while others have remediation plans running to Jan. 10. That makes mid-January the earliest workable mainnet date without specification changes, and late January or early February was described as more realistic.
Dietrichs said waiting until January to decide could move activation to late February or early March, and adopting changes could stretch it to April or May. Such delays would also affect later work, including Hegotá, which is being discussed alongside the network's post-quantum security transition.
Developers are now considering a Hoodi activation around Dec. 16 or 17, after an earlier October test was postponed over compatibility concerns. Execution and consensus teams are expected to decide on the Nov. 26 All Core Developers Consensus call. Those who want changes have been asked to bring specific alternatives backed by impact analysis and auditor feedback beforehand.