
Ethereum developers are leaning toward retaining Glamsterdam’s gas rules despite 200 findings that could disrupt existing smart contracts.
During a Nov. 19 core developers meeting, participants expressed broad support for proceeding with the current specifications rather than introducing changes that could push the network upgrade into April or May 2027.
Developers tentatively targeted the week of Dec. 14 for testing on Ethereum’s Hoodi network, potentially allowing a mainnet activation as early as mid-January. However, the schedule remains unconfirmed as teams address compatibility problems affecting existing applications.
Ethereum’s scaling ambitions expose problems across existing applications
Glamsterdam is designed to significantly expand Ethereum’s capacity, potentially increasing its block gas limit from 60 million to 200 million, a more than threefold increase.
According to Ethereum research firm Ethlabs, the expansion would give applications more room to operate directly on Ethereum’s main network while reducing congestion and transaction fees during periods of heavy demand.
However, achieving that capacity requires changing how Ethereum charges for certain computing operations and data storage.
Two proposals, EIP-8037 and EIP-8038, introduce new gas pricing and accounting rules that could invalidate assumptions built into existing smart contracts.
A ChainSecurity assessment identified 200 compatibility findings across its investigations and work coordinated by the Ethereum Foundation.
Of these, three were classified as high severity, 30 as medium and 167 as low. None was rated critical.
The assessment identified potential disruptions affecting bridges, exchanges, wallets, staking platforms, governance systems, and other infrastructure supporting Ethereum applications.
Most findings can be addressed through configuration changes, but 24 require smart contract upgrades or migrations. Potential consequences include interrupted operations, locked funds, and errors in reward accounting.
The problem stems partly from applications that rely on fixed gas allowances to perform specific operations. Under Glamsterdam’s proposed rules, those allowances may no longer be sufficient to complete the same work.
Recent Juicebox V6 simulations demonstrated the consequences. Some transactions were recorded as successful even though internal payments failed or were skipped under the tested rules.
Ethlabs acknowledged that changing gas prices is necessary to support Ethereum’s expansion but distinguished those changes from accounting modifications that introduced unexpected behavior.
The research firm argued that protocol developers must convince application developers of the upgrade’s safety.
Developers resist changes that could push Glamsterdam to May
Despite the findings, Ethereum developers remain divided over whether modifying Glamsterdam’s specifications would meaningfully improve compatibility.
The Besu client team advocated exploring a targeted revision to EIP-8037 to preserve existing smart contract behavior.
However, Ansgar Dietrichs and several other developers questioned whether a narrow adjustment would resolve enough problems to justify additional testing and development delays.
Marius van der Wijden also warned that changing how gas refunds are handled could disrupt contracts that depend on receiving those refunds during transaction execution.
The disagreement leaves developers choosing between allowing affected applications time to adjust to the existing specifications and redesigning parts of the upgrade to preserve more of their current behavior.
The Ethereum Foundation, alongside security researchers, has contacted more than 50 affected companies. During the meeting, Rahul reported that high-impact projects had completed or were expected to complete fixes by mid-December.
Other affected projects reported remediation schedules extending to Jan. 10, making mid-January the earliest viable mainnet activation window without specification changes.
A late-January or early-February rollout was also discussed as a more realistic possibility.
However, Dietrichs outlined substantially longer timelines if developers postpone their decision to investigate alternative rules.
Waiting until January to decide whether to retain the existing specifications could push activation into late February or early March. Adopting specification changes then could extend the rollout to April or May.
Such delays would also affect Ethereum’s broader upgrade schedule, including preparations for Hegotá, which developers are discussing in connection with the network’s post-quantum security transition.
The competing priorities have strengthened support for maintaining Glamsterdam’s current design.
Developers are now considering a Hoodi activation around Dec. 16 or 17, after an earlier October test was postponed over compatibility concerns.
The proposed gas rules give app teams a working baseline while developers consider revisions.
Hoodi is a public testnet. Mainnet activation timing remains open.
A final decision is expected during the next All Core Developers Consensus call on Nov. 26, when execution and consensus teams will determine whether to proceed with the December test.
Developers advocating changes have been asked to present specific alternatives, supported by impact analysis and auditor feedback, before that meeting.
Approval of the Hoodi schedule would effectively commit Ethereum to testing Glamsterdam’s existing rules, leaving affected application teams to complete their fixes before the upgrade reaches mainnet.













