BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
Altcoins

Glamsterdam Highlights The Limits Of Ethereum’s Upgrade Timeline

Ethereum aims to become an ever faster and more efficient infrastructure. However, its next major update, Glamsterdam, is not expected to arrive on the main network before January 2027 at the

AnonymousCryptoCompass newsroom
November 22, 2026
4 min read
NEWS
Glamsterdam Highlights The Limits Of Ethereum’s Upgrade Timeline
CryptoCompass editorial visual for altcoins coverage.

Ethereum aims to become an ever faster and more efficient infrastructure. However, its next major update, Glamsterdam, is not expected to arrive on the main network before January 2027 at the earliest. Behind this new delay lies a less visible problem than a technical flaw: the protocol’s development pace now exceeds the verification capacity of its teams. This situation raises questions about how Ethereum prepares its evolutions and may force its developers to profoundly reconsider their working methods.

In Brief

  • The delay of Glamsterdam reveals a recurring problem in Ethereum development.
  • The multiplication of technical changes complicates testing and weakens the schedule.
  • Developers are considering smaller updates to speed up deployments without compromising security.

A Technical Output That Exceeds Control Capacities

The assessment by Toni Wahrstätter, researcher at the Ethereum Foundation, is particularly revealing. In his analysis published on November 20, he highlights a growing gap between the speed of code production and the time needed to review its consequences.

Start your crypto adventure safely with OKXThis link uses an affiliate program.

Several indicators illustrate this acceleration :

  • Monthly contributions to technical specifications have doubled to 3.5 times since 2024 ;
  • Glamsterdam required 12 development networks in 160 days, compared to seven in 285 days for Pectra ;
  • The execution layer specifications represent about 6080 lines, compared to 2318 for Prague ;
  • The EIP-8037 proposal includes about 1700 lines of specifications but requires nearly 30000 lines of tests.

These figures highlight a paradox: producing more code and multiplying test environments does not guarantee faster delivery. Teams must also understand interactions between different changes, verify their compatibility, and anticipate the consequences on already deployed applications.

For Wahrstätter, Ethereum notably underestimated this constraint by setting an overly ambitious development schedule.

Glamsterdam, The Price of a Complexity That Has Become Difficult to Manage

The problem is not solely due to Glamsterdam’s size. This update concentrates several important transformations, notably ePBS (Enshrined Proposer-Builder Separation) and Block-Level Access Lists (BALs). Their goal is to improve block production and enable more efficient transaction processing.

This technical ambition multiplies interdependencies between protocol components. Changes must be sufficiently stabilized before deployment on public test networks. However, Glamsterdam recorded ten specification changes in just six weeks after this phase began.

For comparison, previous updates had far fewer changes at this stage. Pectra recorded two and Fusaka only one.

This instability escalated when security researchers identified risks concerning EIP-8037 and EIP-8038. These proposals notably change the way Ethereum charges for certain operations related to the creation and access of on-chain data stored on the blockchain. They could therefore call into question some assumptions embedded in already operational smart contracts.

The delay of activation on Hoodi, initially scheduled for October 26, became necessary to examine these incompatibilities. Developers cannot simply fix the new code without measuring the consequences on existing applications.

The problem is even more significant given that the previous three major Ethereum updates required between 433 and 475 days between finalizing their technical scope and arrival on the main network. Glamsterdam had received just a 320-day schedule.

Ethereum Might Have to Learn to Develop Less to Deliver Better

Beyond Glamsterdam’s schedule, this situation raises a strategic question: Can Ethereum continue to multiply improvements without slowing down its validation process?

Until now, development acceleration was considered an advantage. However, current difficulties show that the ability to produce features is only part of the job. Verification, audits, and compatibility with existing applications become constraints as important as the programming itself.

Toni Wahrstätter thinks that upcoming updates should rely on more realistic timelines, based on the experience of previous deployments. He also recommends setting firm deadlines to abandon unfinished features and stabilize specifications before public testing.

His conclusion summarizes this new direction:

We can certainly deliver faster, but to do so, we must deliver smaller updates.

Developers must now determine whether Glamsterdam can continue its testing schedule. At their meeting on November 19, they discussed December 16 or 17 for a new activation on Hoodi. A decision was expected on November 26. Even in the favorable scenario, a mainnet arrival before mid-January 2027 seems unlikely.

For Ethereum, the challenge goes beyond the postponement of a single update. It is about finding a sustainable balance between innovation, security, and execution capacity without turning every major new evolution into a never-ending project.