Ethereum’s (ETH) planned Glamsterdam network upgrade faces a possible delay stretching into May 2027 as core developers reassess gas-pricing changes that risk interfering with existing smart contracts.
Discussions during a recent All Core Developers meeting highlighted the tension between advancing capacity improvements and preserving the reliable behavior of applications already deployed on the main network.
Participants are evaluating whether to revise key proposals after outreach efforts reached at least fifty organizations whose systems could be affected.
Glamsterdam is the next major hard fork combination in Ethereum’s development sequence.
It pairs execution-layer enhancements aimed at higher throughput and more efficient resource allocation with consensus-layer features that support larger block payloads and better separation of block-construction duties.
A central element involves adjustments to the cost of creating and accessing on-chain state so that fees more closely track the long-term storage and computational burden placed on nodes.
These adjustments are intended to make larger block gas limits sustainable without accelerating uncontrolled growth of the chain’s permanent data set.
Security researchers first flagged potential problems with the gas-repricing proposals in October.
Analysis indicated that certain contracts relying on fixed assumptions about gas consumption could fail or behave differently once the new schedule takes effect.
In response, developers postponed the planned activation on the Hoodi test network that had been set for late October, giving time for deeper examination of real-world impacts.
Subsequent reviews identified concrete examples of contracts that could be disrupted, and a later investigation examined several fundamental invariants—conditions the code assumes will always hold—that the changes might invalidate.
At the Thursday meeting, representatives from the Ethereum Foundation together with independent security firms reported that they had contacted at least fifty companies whose projects appeared potentially exposed.
Of those contacted, three were classified as high-impact, with remediation work either already completed or expected to finish by mid-December.
Medium-impact projects indicated that necessary updates would extend into early January.
Developers noted that any modification introduced to protect one set of contracts risks creating new incompatibilities elsewhere, because many applications embed assumptions about gas accounting that are difficult to alter after deployment, especially when contracts are immutable.
Timing scenarios discussed during the call depend on whether the current specifications remain intact. Under the existing design, activation on mainnet could occur as early as mid-January 2027 once testing resumes.
If the decision on whether to alter the gas proposals is deferred until January, the window would shift to late February or early March.
Adoption of revised specifications would push the earliest feasible mainnet date into April or May.
No final determination was reached at the meeting; further evaluation of both the original proposals and possible alternatives is expected before a binding schedule is set.
The episode underscores a recurring challenge in Ethereum’s upgrade process: balancing protocol-level efficiency gains against the practical constraints of an ecosystem that already contains millions of deployed contracts.
Gas pricing has not undergone a comprehensive overhaul since earlier forks years ago, so the proposed realignment is significant.
While the changes are expected to benefit most ordinary users by enabling higher capacity and more accurate resource pricing, a minority of specialized applications that hard-code gas limits or rely on particular failure-handling patterns may require updates or, in some cases, redeployment.Developers continue to weigh the trade-offs.
Proceeding without modification would allow the capacity improvements to arrive sooner and keep subsequent roadmap items on track, yet it would leave some contracts exposed to unexpected failures or altered economic behavior.
Revising the proposals could reduce those risks but would extend the testing and coordination period, delaying the broader scaling benefits.
Outreach to affected teams remains ongoing, and additional audit results and community feedback are expected to inform the next decision points.
For now though, the Hoodi test-network activation remains unscheduled, and mainnet timing is provisional.
Node operators, application developers, and other stakeholders are being encouraged to review their contracts against the documented invariants and to prepare contingency plans. The outcome will determine whether Glamsterdam delivers its intended efficiency gains in the first quarter of 2027 or later in the spring.
