f71f677b-8
Ethereum’s Glamsterdam upgrade may slip to May 2027
Ethereum may delay Glamsterdam to April or May 2027 after a compatibility review reached at least 50 affected companies, while a separate post-quantum fork faces scope questions.

Outputs
The Ethereum Foundation, ChainSecurity and Dedaub jointly contacted at least 50 affected companies.
Three high-impact projects have fixes completed or expected by mid-December.
Medium-impact projects reported remediation timelines extending to January 10.
A deferred decision could move Glamsterdam from mid-January 2027 to late February, early March, April or May.
Client teams are expected to submit Hegotá positions ahead of discussions in two weeks.
By Nathan Brooks
Ethereum’s Glamsterdam upgrade could activate in April or May 2027 if developers modify its specifications to reduce compatibility risks, according to Thursday’s developer meeting. Under the existing design, mainnet activation could come as early as mid-January 2027. Deferring the decision until January could instead move activation to late February or early March, even without a specification change.
The compatibility review has reached at least 50 affected companies. Developers said the Ethereum Foundation, ChainSecurity and security firm Dedaub collectively contacted those companies. Three projects were classified as high impact, with fixes either completed or expected by mid-December. Medium-impact projects reported timelines extending to January 10.
The “at least” designation makes 50 a lower bound rather than a final tally, so remediation work could extend beyond the companies identified so far. That makes the December and January milestones operational markers, not evidence that the wider compatibility review has closed.
Developers debated whether to retain Glamsterdam’s existing specifications or modify them. Their concern was direct: “Every spec change could, again, break new invariants that we are not aware of breaking yet,” one developer warned during the meeting. Changes intended to protect some contracts could disrupt others, turning a compatibility safeguard into another source of implementation risk.
The central trade-off is not a simple choice between speed and safety. Retaining the current specifications keeps mid-January as the earliest activation scenario, but the modifications under discussion target compatibility risks already identified. Altering the design, however, could introduce other failures, which is why developers have not settled on a final specification or date.
What does this change for contract teams?
It changes the interval between remediation and a dependable activation date. High-impact projects have fixes completed or due by mid-December, while medium-impact work can continue through January 10.
For teams, the practical consequence is continued schedule uncertainty. Postponing the specification choice could add roughly six weeks to the earliest activation scenario, with April or May available if the upgrade changes.
The six-week estimate compares mid-January with late February or early March; it does not assume an exact activation day. No decision has been reached, so the current schedule remains a set of planning scenarios rather than a committed launch date.
Teams exposed to high-impact changes have the clearest near-term deadline, but a late specification decision could reopen compatibility work after earlier fixes. The mid-January option remains the earliest scenario under the existing specifications.
Hegotá’s post-quantum scope remains unsettled
Separately, Hegotá, Ethereum’s next planned hard fork, could see its scope reduced as the network seeks to accelerate its transition to post-quantum cryptography. Developers considered postponing some Ethereum Improvement Proposals, or EIPs, to prioritize post-quantum features. Several argued that reducing the upgrade’s scope offers little benefit unless the change also shortens the rollout timeline.
Developers also raised compatibility concerns over EIP-8151, a proposal designed to protect accounts migrating to post-quantum security. A preliminary review identified a potentially large number of existing smart contracts that could be affected by the changes, complicating the proposal’s inclusion in Hegotá. The concern therefore extends beyond account migration and touches existing contract integrations.
No decision was reached on Hegotá’s scope. Client teams are expected to submit their positions ahead of further discussions two weeks from the meeting. That submission window is the next concrete deadline for teams shaping the fork; until the follow-up discussion, Glamsterdam’s activation date and Hegotá’s feature set remain unsettled.
via cryptonews.net (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,651 articles