
Ethereum Glamsterdam Delay Could Push Upgrade to May 2027 Over Gas Compatibility
Ethereum’s next major upgrade, the Glamsterdam hard fork, could be pushed back as far as May 2027 if developers decide to rewrite its specifications to address smart contract compatibility problems, according to discussions at Thursday’s All Core Developers meeting. A security review found the proposed changes to how Ethereum charges for storing data could disrupt thousands of existing smart contracts, some unupgradeable. Under the current specifications, the upgrade could reach the main network as early as mid-January 2027, but modified gas pricing rules could push activation to April or May 2027. The Ethereum Glamsterdam delay is not yet decided, and the meeting ended without a decision, but the debate frames a stark choice: ship on time and risk breaking live applications, or delay and protect them.
Glamsterdam is a planned hard fork to increase Ethereum’s capacity and efficiency. Its centrepiece is a pair of proposals that rework how the network charges for gas, the fee paid for every computation and piece of data stored on the blockchain. Those proposals, known as EIP-8037 and EIP-8038, are designed to let the block gas limit rise from about 60 million to as much as 200 million, roughly 3.3 times the current capacity. That would allow far more activity in each block, but the same changes would raise the cost of many existing operations, and that is where the trouble begins.
Ethereum gas repricing: the two proposals at the centre
EIP-8037 and EIP-8038 change how Ethereum prices new state, the permanent data every node must store forever. Today, creating a new storage slot costs 20,000 gas and creating a new account costs 25,000 gas. Under EIP-8037, a new storage slot would cost 97,920 units of state gas, up from 20,000, and a new account would cost 183,600, up from 25,000. The specification prices a 24-kilobyte contract deployment at about 37.8 million gas, up from roughly 4.9 million today. EIP-8037 also splits gas into two pools, execution gas and a separate state-gas reservoir. The repricing exists to keep the network’s stored data in check.
The logic is straightforward. Every byte stored on Ethereum has to be kept by thousands of nodes forever, and the cost of that storage has long been underpriced relative to the burden it creates. By charging more for state creation, the proposals aim to slow state growth and make the higher gas limit safe. The problem is that thousands of existing smart contracts were written assuming gas costs would stay roughly where they are. Many hardcode gas values, rely on fixed gas stipends or branch their logic on how much gas remains, and when those assumptions change, the contracts can stop working even though their code has not changed.
The warning: up to 15,000 contracts could break
The scale of the problem became clear on Monday, November 16, when Ethereum Foundation developer Marius van der Wijden told core developers the two gas-pricing proposals could break 10,000 to 15,000 smart contracts. The estimate is an upper bound, not a confirmed count; van der Wijden presented no verified inventory. He described them as a small fraction of Ethereum’s roughly 90 million smart contracts, with value at risk in the low hundreds of thousands of dollars. But the headline number dominated the discussion. Some affected contracts cannot be upgraded at all, so they would have to be redeployed from scratch, which is not always possible when a contract holds funds or depends on an address that other contracts already trust.
The patterns that make contracts vulnerable are well understood, and the Ethereum Foundation has flagged eight smart contract invariants for builders to check, including fixed 2,300-gas stipends, hardcoded gas values and presigned transactions with fixed gas limits. These are common patterns in contracts written over many years. The audits tie most of the breakage to gas costs rather than to new mechanics, which means code that never changes can still stop working. Developers cannot simply patch the affected contracts, because in many cases the people who wrote them are gone, or the contracts are immutable by design.
What the audits found
The concerns first surfaced in October, when security firm ChainSecurity warned that the proposed gas pricing changes could disrupt existing smart contracts and potentially expose them to exploitation. Developers postponed the Hoodi testnet fork, originally scheduled for October 26, and it remains on hold. ChainSecurity disclosed 13 deployed mainnet contracts as real-world examples in October. ChainSecurity and Dedaub presented audit findings that identified about 200 distinct classes of affected contracts, most tied to higher gas costs rather than to the new accounting mechanics. The 200 classes and the 15,000 contracts measure different things: the audits map the kinds of breakage to expect.
Since then, the Foundation, ChainSecurity and Dedaub have collectively contacted at least 50 affected companies, according to Thursday’s meeting. Three projects were classified as high impact, with fixes done or expected by mid-December, while medium-impact projects reported timelines to January 10. That outreach has reduced the immediate risk, but it has not resolved the underlying question. Van der Wijden said planned public outreach had slipped amid reorganisations and budget cuts at the Foundation. A hard fork that breaks live applications would damage Ethereum’s reputation for stability, one of its most valuable assets.
Ethereum Glamsterdam delay: the timeline choices
Developers now face three broad paths, each with a cost. Under the current specifications, mainnet activation could come as early as mid-January 2027, the fastest option but the riskiest for compatibility. Waiting until January to decide could push activation to late February or early March, even without specification changes, because testing takes time. Adopting modifications could push activation to April or May 2027, developer Ansgar Dietrichs estimated, as reported by The Defiant. No decision has been reached. One developer warned that every specification change could break new invariants developers are not yet aware of, which captures the dilemma: fixing the known problems could create unknown ones.
Several developers argued that removing the gas repricing proposals would delay Glamsterdam and the post-quantum roadmap by four to six months, a powerful argument for keeping them. The repricing is what makes the higher gas limit safe; without it, Glamsterdam’s capacity gains would be harder to justify. Others argued that shipping a hard fork known to break thousands of contracts would be worse than a delay. The Hoodi testnet fork stays on hold, so there is still no confirmed date. Glamsterdam will arrive when the developers are confident it is safe, and that confidence is not yet there.
Hegota and the post-quantum question
The debate over Glamsterdam is tangled up with the upgrade that follows it. Ethereum’s next planned hard fork, Hegota, could see its scope reduced as the network seeks to accelerate its transition to post-quantum cryptography, the security standards needed against future quantum computers. During Thursday’s meeting, developers considered postponing some Ethereum Improvement Proposals to prioritise post-quantum features, though several argued that would help little unless it also shortened the rollout. Developers also raised compatibility concerns over EIP-8151, a proposal to protect accounts migrating to post-quantum security, after a preliminary review found many existing contracts could be affected. No decision was reached on Hegota’s scope; client teams will submit their positions ahead of further discussions in two weeks.
The post-quantum question is the same kind of problem as the gas repricing, only larger. Changing the cryptography that secures accounts could break far more contracts than changing gas prices, and the work has to start years before quantum computers become a practical threat. Glamsterdam shows how hard it is to change the rules of a network hosting millions of applications. The two debates are connected: a delay to Glamsterdam pushes back Hegota, and protecting existing contracts in one upgrade sets a precedent for the next.
The market backdrop
The upgrade debate is unfolding against a weak market for ether. Ethereum traded at about $1,754 on November 20, down 1.1 percent over 24 hours and 12.9 percent over seven days, with a market capitalisation of about $214 billion. The token has fallen about 28 percent over the past 30 days and sits more than 60 percent below its all-time high of about $4,946. United States spot ether funds recorded $29.1 million in net outflows on November 17, a second straight day of redemptions, and five-session outflows reached $250.5 million. Earlier, ether funds lost $398.9 million in the week ended November 13, a seventh straight weekly outflow. The weakness is driven mainly by the broader selloff in risk assets, not the upgrade debate.
For holders of ether, the short-term implications are limited: a delayed hard fork does not change how the network works today. The longer-term implications are more significant: Glamsterdam is meant to raise Ethereum’s capacity and keep it competitive with faster rival networks, and a delay pushes those gains further into the future. On the other hand, a hard fork that breaks live applications would be far more damaging than a delay, and the developers’ caution shows they take that risk seriously. Delays are common and usually forgotten once an upgrade ships safely; the upgrades remembered are the ones that went wrong.
Frequently asked questions
What is the Glamsterdam upgrade? Glamsterdam is a planned Ethereum hard fork to increase the network’s capacity and efficiency. Its centrepiece is a rework of gas pricing, through EIP-8037 and EIP-8038, designed to let the block gas limit rise from about 60 million to as much as 200 million.
Why might Glamsterdam be delayed until May 2027? Developers are weighing whether to rewrite the gas pricing specifications after audits found they could break 10,000 to 15,000 smart contracts. Keeping the current specifications could allow activation from mid-January 2027, but adopting changes could push it to April or May 2027.
Which contracts are at risk? Contracts that hardcode gas values, rely on fixed 2,300-gas stipends, branch on remaining gas or use presigned transactions with fixed gas limits are most vulnerable. The Foundation has flagged eight such patterns, known as invariants, for builders to check.
What happens next? The Hoodi testnet fork remains on hold, and developers will revisit the question at upcoming All Core Developers calls. No decision has been reached on the gas proposals or on Hegota’s scope.
Source: Cointelegraph
—
Related reading on MM Crypto Analysis Web
- $137 Million in Stolen Binance ETH Moves Through THORChain, Lookonchain Reports
- Ethereum Wins the Venue in Asia but Loses the Settlement Layer, Analysis Finds
- Ethereum May Retest $1,500 as ETF Outflows Hit $2.4 Billion in Seven Weeks
More in Ethereum on MM Crypto Analysis Web.
Pingback: Ethereum MEV Acquittal: MIT Brothers Cleared in $25M Case