The Glamsterdam upgrade for Ethereum may arrive not in the middle of January 2027 but only in May. At Thursday's All Core Developers meeting on November 19, developers discussed whether to change the fork's specification so it does not break smart contracts that already run on the network. No decision has been made.
In numbers, at least 50 companies have been warned, three projects are rated high risk, and the first fixes are expected by the middle of December. How long the rest take will decide the launch date.
A spread of four months, from January to May
Glamsterdam is a planned Ethereum protocol upgrade meant to raise the network's capacity and efficiency. The schedule has already slipped. In October, ChainSecurity, a firm that audits blockchain security, warned that proposed changes to gas pricing could disrupt existing contracts and leave them open to exploitation. As a result, developers postponed the fork on the Hoodi test network, which had been set for October 26.
If the specification stays as it is, mainnet could be upgraded as early as the middle of January 2027. If the decision waits until January, activation slides to late February or early March. And if the specification does get edited, the target is April or May. Between the earliest and the latest scenario lie roughly four months.
What gas repricing breaks
The trouble sits in two proposals, EIP-8037 and EIP-8038. Both change the cost of gas, the fee paid for running operations on Ethereum. Contracts are written with a certain cost in mind, and when it shifts, some of the authors' assumptions stop holding.
Researchers measure the scale in concrete cases. In October they found 13 real contracts that could be affected. A November review went deeper and examined eight smart contract invariants, meaning conditions that are supposed to hold at all times but could fail after the upgrade. The more of those conditions are at risk, the harder it is to guarantee that no contract breaks unnoticed.
At least 50 companies and three projects rated high risk
The Ethereum Foundation, ChainSecurity and the security firm Dedaub together contacted at least 50 companies whose contracts could be hit by the changes. Developers sorted them by level of impact. Three projects were rated high risk, and their fixes are either done or due by the middle of December.
Projects with medium impact quote longer timelines, up to January 10. So even in the fastest scenario only a few days separate the last deadline from a possible activation in the middle of January. That is why the calendar is so tight.
Three scenarios and four checkpoints
There are two ways to deal with the problem. Keep the specification and wait for projects to update their contracts, or change the fork itself. The second route has a price too. Changes that protect some contracts can hit others. One developer said at the meeting: "Every spec change could, again, break new invariants that we are not aware of breaking yet".
That leaves three scenarios.
- Specification unchanged: activation is possible in the middle of January 2027 if every project makes it in time.
- Decision pushed to January, activation in late February or early March.
- Specification edited, and then it is April or May, and the new edits must be checked for compatibility again.
Lay the news out by date and four marks appear. Around December 3, two weeks after the meeting, client teams are due to state their positions on Hegotá. By the middle of December the fixes from the three projects rated high risk are expected. By January 10 the projects with medium impact give their timelines. Only after that can anyone talk about activating Glamsterdam, which in the fastest case lands in the middle of January.
So developers have no slack. A delay at any one of these marks pushes the next one automatically. That is why talk of May does not look like an exaggeration. It is the logical result if the specification is changed after fresh compatibility checks.
Hegotá, quantum protection versus the size of the upgrade
Separately, developers discussed the next fork, Hegotá. Its scope could be cut to move faster to cryptography that resists quantum computers. Some proposals are being considered for postponement to free up room for quantum defense features. Several participants objected, though, saying that trimming the scope would gain little unless the rollout timeline is shortened as well.
It has its own compatibility problem too. A preliminary review of EIP-8151, a proposal meant to protect accounts during the move to protection against quantum attacks, found that it could affect a potentially large number of existing contracts. Client teams are due to send their positions on Hegotá's scope before the next discussion, in about two weeks.
Four months of spread and two open decisions
A January 2027 start for Glamsterdam remains possible, but only if the specification is left alone and the three projects rated high risk close their gaps by the middle of December. Every edit moves the date by months. A separate decision on Hegotá's scope is also pending, and it will set the pace of the network's plans for quantum defense. The fork date does not set the exchange rate directly, so anyone thinking about how to sell Ethereum for hryvnia will gain more from comparing live rates than from watching the developers' calendar.




Comments
Your email address will not be published. Required fields are marked *