In this article5 sections
Ethereum’s next major hard fork will not reach mainnet in 2026, and developers are now weighing a window as late as April or May 2027 depending on whether they rewrite the upgrade’s gas-pricing rules. According to Bitcoinist, the Glamsterdam schedule has already absorbed a testnet postponement and a fresh round of compatibility warnings.
The Ethereum Foundation said in its official update on the two proposals that security researchers flagged problems with existing smart contracts during testing. At the Nov. 19 All Core Developers meeting, developers said the foundation, ChainSecurity and Dedaub had collectively contacted at least 50 affected companies.
Also readEthereum Glamsterdam Nears First Public Test: Sepolia Set for Oct. 6
Key facts
- The Hoodi testnet fork, originally set for Oct. 26, was postponed; developers tentatively proposed activating it on Dec. 16 or 17 during the week of Dec. 14.
- ChainSecurity’s Nov. 18 assessment, reported by crypto.news, disclosed 200 findings: three high severity, 30 medium and 167 low, with none critical.
- EIP-8037 would raise the base state charge for creating a smart contract from 32,000 to 183,600 gas units, before execution and code-storage costs.
- Three high-impact projects have fixes done or expected by mid-December; medium-impact work extends to Jan. 10, per Cointelegraph.
- Twenty-four findings require smart contract upgrades or migrations rather than configuration changes.
Three possible activation windows
The timetable now branches on a single question: do developers keep Glamsterdam’s current specifications or amend them? According to Cointelegraph and crypto.news, retaining the existing rules allows mainnet activation as early as mid-January 2027, though Ansgar Dietrichs, who chaired the meeting, called late January or early February more realistic. Deferring the specification decision until January would move the rollout to late February or early March even under unchanged rules. Adopting revised specifications at that point could push activation to April or May, because client teams would need time to implement and test the edits.
Client positions split. Geth, Nethermind, Reth and ethrex favored keeping the current rules, Erigon preferred modifications, and Besu voiced reservations while indicating it could proceed as drafted, per crypto.news.
Also readCurve: Glamsterdam Could Ease DeFi Congestion on Ethereum
Where the compatibility risk sits
EIP-8037 and EIP-8038 reprice operations that touch Ethereum’s permanent database. EIP-8037 raises the cost of creating new state; EIP-8038 addresses the cost of reading and modifying existing state, with its authors arguing the database has grown heavier since the Berlin upgrade in March 2021. Applications built around the old gas costs can misbehave once those assumptions change.
Affected systems include exchanges, wallets, bridges, staking protocols and governance applications, with consequences ranging from operational interruptions to locked funds and incorrect reward calculations. Marius van der Wijden, an Ethereum Foundation developer, warned that as many as 15,000 programs could potentially be affected, according to Bitcoinist. Cointelegraph and crypto.news both report that developers contacted at least 50 companies; ChainSecurity logged 13 real-world examples of vulnerable contracts in October and eight potentially broken smart contract invariants in a November review. The outlets differ on the furthest-out date: Cointelegraph and crypto.news cite May 2027, while Bitcoinist frames January or February 2027 as the realistic window.
Toni Wahrstätter, an Ethereum researcher quoted by crypto.news, cautioned that edits meant to shield one set of contracts could expose another: any specification change could break invariants nobody has identified yet.
Why it matters
Glamsterdam is the vehicle for a proposed jump in the block gas limit from roughly 60 million to 200 million, more than a threefold lift in theoretical capacity, and for faster transaction processing and block validation. Every month of slippage leaves that headroom unclaimed on mainnet. The friction is also a reminder that high-throughput changes to base-layer accounting can reach deep into live applications, so a postponed fork avoids shipping breakage to production at the cost of a later capacity increase.
What to watch
Consensus-layer developers meet again on Nov. 26, when teams seeking changes must bring a concrete alternative and participants are expected to decide whether the December Hoodi rehearsal proceeds. Client teams are also due to submit their preferred scope for the next fork, Hegotá, ahead of further talks in two weeks, with quantum-resistant cryptography and a compatibility review of EIP-8151 on the agenda.
Sources: Bitcoinist, Cointelegraph, crypto.news




