Why Ethereum Glamsterdam Upgrade Faces Delay Risk Until May 2027

9 min read
2 views
Nov 20, 2026

Ethereum developers just revealed Glamsterdam could slip all the way to May 2027. Two gas-pricing changes triggered 200 compatibility findings across exchanges, wallets and bridges. The real decision still hangs in the balance and the next two weeks will decide everything.

Financial market analysis from 20/11/2026. Market conditions may have changed since publication.

I’ve been following Ethereum upgrades long enough to know that timelines almost never stick the way people hope. Still, the latest signals around Glamsterdam feel different. What started as a reasonably confident plan for a late-2026 or very early-2027 activation now carries a realistic chance of sliding all the way into May. The reason isn’t some dramatic technical failure. It’s something quieter and more awkward: hundreds of existing applications simply weren’t built for the new gas-pricing rules.

What Actually Happened in the Latest Developer Call

During the most recent All Core Developers discussion, the conversation shifted from optimistic scheduling to careful damage assessment. Teams had already begun reaching out to projects that would feel the impact of two specific proposals. Those proposals change how much gas it costs to create new state and how much it costs to read or modify existing state. On paper the changes look sensible. In practice they collide with years of assumptions baked into live smart contracts.

Security researchers working with the Foundation finished a coordinated review and came back with roughly two hundred findings. Three of them ranked high severity. Thirty sat in the medium bucket. The rest were lower priority but still real. None of the issues rose to critical, which is good news, yet the sheer volume means a lot of teams now have homework.

At least fifty companies received direct contact. Exchanges, wallet providers, bridges, staking services and governance tools all appear on the list. Some of the problems can be fixed with configuration tweaks. Roughly two dozen, however, require actual contract upgrades or migrations. That kind of work does not happen overnight, especially when the contracts already hold meaningful value.

The Two Proposals Creating the Friction

The first proposal raises the cost of creating new state. Deploying a fresh contract or writing new information into storage becomes noticeably more expensive. The base charge for contract creation jumps from the familiar 32,000 gas units to something closer to 183,600 before any execution costs are added. Developers who wrote systems under the old pricing model suddenly face different economic realities.

The second proposal targets the cost of accessing and changing existing state. Ethereum’s permanent database has grown substantially since the Berlin upgrade years ago. Certain operations now consume more resources than they once did, and the network wants the gas schedule to reflect that reality. Fair enough in theory. The trouble is that many applications were carefully tuned around the previous numbers. Change the numbers and some of those applications start behaving in unexpected ways.

I’ve seen this pattern before with other networks. You adjust a fee parameter that feels minor, and suddenly a whole class of contracts that relied on tight gas limits starts failing or becoming uneconomical. The difference here is the scale. Ethereum still carries the largest concentration of complex, high-value applications in the entire industry. A change that touches state costs touches almost everything.

Three Possible Launch Windows on the Table

Right now developers are looking at three rough timelines. The earliest realistic mainnet window sits in mid-January if everyone keeps the current specifications and the affected teams finish their fixes on schedule. Many of the high-severity cases are expected to clear by mid-December. Medium-severity items stretch into early January. That path still feels aggressive but not impossible.

A more cautious view points to late January or early February. Waiting until January before deciding whether the specifications need adjustment would push the schedule further. Even if the rules ultimately stay the same, the extra decision time adds weeks.

The third path is the one that worries people most. If the community decides the current gas rules create too much disruption and must be revised, client teams will need time to implement and test the new version. That scenario stretches mainnet activation into April or even May. Nobody wants that outcome, yet it remains on the board.

Every specification change could break new invariants that we are not yet aware of.

That caution from one of the researchers captures the tension perfectly. Changing the rules to fix today’s problems risks creating tomorrow’s problems. Most execution client teams currently prefer sticking with the existing specifications. A couple of teams have reservations, and one has expressed a clear preference for modifications. The next consensus-layer call will carry real weight.

Testnet Rehearsals Still Planned for December

Even while mainnet timing remains fluid, developers still want a December rehearsal on the Hoodi testnet. Dates around the 16th and 17th are under discussion. Earlier plans for an October activation on that network had to be postponed after researchers spotted problems with existing mainnet contracts. That postponement also delayed a planned increase of the testnet block gas limit.

Running the upgrade on a public testnet in December gives everyone a live stress test before any irreversible mainnet decision. Teams that still want specification changes have been asked to prepare concrete alternatives ahead of the next meeting. The community is trying hard to avoid a last-minute scramble.

Why Gas Pricing Changes Matter More Than They Appear

Gas has always been Ethereum’s way of measuring and charging for computational effort. Over time the network has accumulated layers of complexity. State growth is one of the thorniest long-term challenges. Every new contract and every new storage slot adds permanent data that nodes must carry forever. Making the creation of that state more expensive is a rational response.

Yet rationality on the protocol level can look like breakage on the application level. Consider a staking protocol that carefully calculated how much gas its reward distribution would consume under the old rules. Raise those costs and the same distribution might suddenly fail or become so expensive that users stop participating. A bridge that batch-processes messages could hit unexpected limits. A governance contract that assumes a certain gas ceiling for voting might lock up.

Most of these situations are recoverable. Configuration changes, parameter updates, or carefully planned migrations can solve them. The difficulty lies in coordination. Fifty different teams cannot all move at the same speed. Some contracts are immutable by design. Others sit behind multi-signature processes that take weeks. The more complex the dependency graph, the longer the tail of residual risk.

Client Team Preferences and the Path Forward

Execution client teams hold a lot of practical power in these decisions. Their code has to implement whatever the community ultimately chooses. In the latest discussion the majority leaned toward keeping the current specifications. That preference makes sense. Changing course this late introduces new testing burdens and new uncertainty.

Still, the minority view deserves attention. If the current rules create systemic friction for a meaningful slice of the ecosystem, pushing ahead could damage trust. Ethereum’s culture has always tried to balance progress against caution. This moment is testing that balance again.

I find myself more sympathetic to the careful side right now. The network has grown large enough that rushing creates externalities that used to be manageable. A few extra months of delay is painful for narrative and for teams waiting on new features, yet it is still cheaper than a messy mainnet activation followed by emergency patches.

Looking Beyond Glamsterdam to the Next Fork

While Glamsterdam occupies the immediate spotlight, developers also spent time discussing the subsequent hard fork. There is growing interest in narrowing its scope so that quantum-resistant cryptography work can move faster. One approach gaining quiet support would allow advanced verification techniques without forcing an entirely new programming model onto the network.

Even that conversation carries its own compatibility clouds. A draft proposal intended to protect accounts after they migrate to post-quantum security appears capable of affecting a large number of existing contracts. Preliminary checks already show potential breakage. Execution teams will need to submit preferred scopes before deeper discussion continues.

The pattern is familiar. Every major change that touches account abstraction, cryptography, or state management risks colliding with the living history of the chain. Ethereum’s strength is its accumulated application layer. That same strength makes every upgrade more delicate.

Practical Implications for Builders and Users

If you run an application that touches state creation or heavy storage access, the next few weeks matter. Review the current gas assumptions in your contracts. Check whether any critical paths sit close to gas limits that will change. Talk to your auditors early. Migration planning is rarely fun, yet it is far better than discovering a problem on mainnet.

For ordinary users the immediate impact should stay limited. Most day-to-day interactions will continue working. The risk sits more with sophisticated protocols that operate close to the economic edge of the gas schedule. Still, any prolonged delay in Glamsterdam also delays whatever benefits the upgrade was expected to deliver. Progress on state management and long-term sustainability moves slower when the network has to pause for compatibility work.

I’ve spoken with a few teams already preparing contingency plans. Some are writing dual-path code that can adapt to either the current or a revised specification. Others are simply waiting for clearer signals before committing engineering time. That wait-and-see attitude is understandable, yet it also contributes to the overall slowdown.

The Broader Context of Ethereum’s Upgrade Cadence

Ethereum has never been the fastest-moving chain, and that is partly by design. The community has repeatedly chosen deliberate progress over rapid iteration when the stakes involve irreversible mainnet state. Previous upgrades taught hard lessons about the cost of underestimating edge cases. Those lessons are visible in the current careful tone.

At the same time, the network faces competitive pressure. Other ecosystems ship features more aggressively. Users and developers sometimes grow impatient with multi-year roadmaps. Balancing those pressures is never easy. Glamsterdam was supposed to be a relatively focused upgrade. Compatibility realities have expanded its effective scope and timeline.

Perhaps the most interesting aspect is how openly the process is unfolding. The findings, the outreach to fifty companies, the internal debates about timelines—all of it is happening in public. That transparency is valuable even when the news is inconvenient. It lets the broader ecosystem prepare instead of being surprised.

What the Next Two Weeks Will Decide

The immediate calendar is clear. Teams that want specification changes need to present concrete alternatives before the next consensus-layer meeting. That meeting will largely determine whether the December testnet rehearsal proceeds under the current rules. A decision to keep the existing specifications would keep the mid-January mainnet window alive. A decision to revise would start the longer path toward spring.

I expect most teams will ultimately prefer the path of least disruption. Changing gas rules late in the cycle introduces new unknowns, and the network already has enough of those. Yet I also expect the conversation around state growth costs to continue. The underlying economic pressure does not disappear just because the current proposals create friction.

In the end this episode is less about any single upgrade and more about the maturing reality of Ethereum. The chain is no longer a small experimental network where breaking changes can be absorbed quietly. It is a global settlement layer carrying serious economic activity. Adjustments that once felt routine now require months of coordination. That is both a success story and a constraint.

Whether Glamsterdam lands in January, February, or May, the process itself is revealing. The network is learning, sometimes the hard way, how to evolve without leaving its own history behind. For anyone building on Ethereum, that lesson is worth watching closely. The next few developer calls will tell us a great deal about how the community intends to handle similar tensions in the upgrades that follow.


The coming weeks will not be quiet. Security researchers will keep digging. Application teams will keep patching. Client developers will keep testing. And the rest of us will keep watching the calendar, hoping the final date lands closer to the optimistic end of the range than the pessimistic one. Ethereum has navigated harder moments than this. Still, every delay carries a cost in momentum and attention. Getting the gas rules right matters. Getting them right without breaking the living ecosystem matters more.

In my view the healthiest outcome is the one that preserves the broadest set of existing applications while still making meaningful progress on state economics. That outcome may require a little more patience than many of us would like. Patience has rarely been the wrong bet on this network. The question now is how much patience the community is willing to show before the next hard fork finally activates.

❝
Investing isn't about beating others at their game. It's about controlling yourself at your own game.
— Benjamin Graham
Author

Steven Soarez passionately shares his financial expertise to help everyone better understand and master investing. Contact us for collaboration opportunities or sponsored article inquiries.

Related Articles

?>