711df98b-b
Ethereum's Glamsterdam Upgrade Faces Slip to May 2027
Ethereum developers say Glamsterdam could activate as late as May 2027 if gas repricing specs change, after outreach to 50 firms over contract breakage risks from EIP-8037 and EIP-8038.

Outputs
Glamsterdam mainnet activation could slip to April or May 2027 if spec changes are adopted; current specs allow mid-January 2027.
ChainSecurity, the Ethereum Foundation and Dedaub contacted at least 50 affected companies; three projects rated high impact with fixes due by mid-December.
Gas repricing proposals EIP-8037 and EIP-8038 were linked to 13 real-world affected contracts identified in October; the Hoodi testnet fork set for Oct. 26 was postponed.
Medium-impact projects reported fix timelines extending to Jan. 10.
The next hard fork, Hegotá, may shrink in scope to prioritize post-quantum features; client teams submit positions before discussions resume in two weeks.
Ethereum's Glamsterdam hard fork could slip to May 2027 if developers modify its specifications to fix smart contract compatibility problems, according to discussions at Thursday's All Core Developers (ACD) meeting.
Under the current specifications, mainnet activation could arrive as early as mid-January 2027. But that window narrows fast. Waiting until January to decide could push activation to late February or early March — or to April or May if spec changes are adopted. No decision has been reached.
The trouble started in October. Blockchain security firm ChainSecurity warned that proposed changes to Ethereum's gas pricing could disrupt existing smart contracts and potentially expose them to exploitation. That warning forced developers to postpone the Hoodi testnet fork, originally scheduled for Oct. 26.
Which proposals are causing the problem?
The concerns center on two gas repricing proposals: EIP-8037 and EIP-8038. Researchers identified 13 real-world examples of potentially affected contracts in October. A November investigation went deeper, examining eight smart contract invariants that the upgrade could disrupt.
The outreach effort has been substantial. During Thursday's meeting, developers said the Ethereum Foundation, ChainSecurity and security firm Dedaub had collectively contacted at least 50 affected companies.
- Three projects were classified as high impact, with fixes completed or expected by mid-December.
- Medium-impact projects reported remediation timelines extending to Jan. 10.
- At least 50 companies have been contacted across the coordinated effort.
The operational stakes are straightforward. A repriced opcode can turn a contract that worked for years into an exploitable one. That is why the Hoodi testnet fork was pulled, and why the calendar is now in question.
What does the spec debate actually turn on?
Developers are weighing whether to retain Glamsterdam's existing specifications or modify them to reduce compatibility risks. The catch: changes intended to protect some contracts could disrupt others.
One developer put the risk bluntly during the meeting: "Every spec change could, again, break new invariants that we are not aware of breaking yet."
That is the core dilemma. Keep the specs, and the 13 identified contracts plus any undiscovered ones absorb the repricing shock. Change the specs, and developers gamble on finding every invariant the modification itself would disturb. Either path carries a compatibility tail risk that only coordinated outreach can surface, which is why the 50-company contact effort matters as much as the engineering itself.
For application teams, the practical consequences are concrete. Any protocol whose gas assumptions are baked into assembly-level code or gas-gated logic must audit against EIP-8037 and EIP-8038 before activation. The mid-December and Jan. 10 fix deadlines give a rough map of how long that work takes in the wild.
Hegotá and the post-quantum squeeze
A second conversation ran in parallel at Thursday's meeting. Bureaucratically, it sits one fork ahead. Ethereum's next planned hard fork, Hegotá, could see its scope reduced as the network pushes to accelerate its transition to post-quantum cryptography.
Developers considered postponing some Ethereum Improvement Proposals to prioritize post-quantum features. Not everyone bought the trade. Several argued that reducing the upgrade's scope would offer little benefit unless it also shortened the rollout timeline.
EIP-8151 drew its own compatibility flags. The proposal is designed to protect accounts migrating to post-quantum security, but a preliminary review identified a potentially large number of existing smart contracts that could be affected by the changes. That finding complicates its inclusion in Hegotá.
No decision was reached on Hegotá's scope either. Client teams are expected to submit their positions ahead of further discussions in two weeks, which sets the next concrete checkpoint for both forks — and the earliest signal of whether Glamsterdam holds its January window or drifts toward spring 2027.
via eips.ethereum.org (Original)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,581 articles