Markets
BTC $55,872 -9.05% ETH $1,550 -9.99% BNB $511 -9.71% XRP $0.8764 -8.47% SOL $65.57 -8.93% LINK $8.11 -7.46% BTC $55,872 -9.05% ETH $1,550 -9.99% BNB $511 -9.71% XRP $0.8764 -8.47% SOL $65.57 -8.93% LINK $8.11 -7.46% TOTAL $1.96T BTC.D 57.3%

Ethereum

Ethereum’s Glamsterdam Upgrade Slips Into 2027 as Gas Repricing Breaks Apps

Two proposals to charge more for state would make some contracts fail, so developers are weighing January, March or a rewrite that pushes the fork to spring.

Ethereum will not activate its next hard fork in December. On the Nov. 19 All Core Developers call, the earliest possible mainnet launch of Glamsterdam was pushed to January 2027, and developers laid out a route that ends in April or May if the upgrade’s gas rules are revised.

The obstacle is not a client bug. It is the cost of storing data. Two proposals, EIP-8037 and EIP-8038, change what the network charges for operations that touch its permanent database. Under EIP-8037’s current specification, the state-related charge for creating a contract would rise from 32,000 gas units to 183,600, on top of the separate execution charge. EIP-8038 covers the cost of reading and modifying state that already exists; its authors argue the database has grown heavy enough since the Berlin upgrade in March 2021 to justify higher prices.

Applications built around the old numbers may not simply pay more. They can fail to execute. Ethereum Foundation developer Rahul Kothari told the call that the foundation, ChainSecurity and Dedaub had contacted at least 50 companies affected by the change, and that a ChainSecurity assessment completed on Nov. 18 recorded 200 findings: three high severity, 30 medium and 167 low, with none critical.

The remediation schedule is what moves the date. Kothari said the three high-severity cases had been addressed or were expected to be resolved by mid-December, while projects working through medium-severity issues gave completion dates extending to Jan. 10. If the specifications stay as they are, mid-January becomes the earliest mainnet window. Ansgar Dietrichs, who chaired the meeting, called late January or early February more realistic.

Waiting until January to decide whether the rules should change adds a second delay even if developers end up keeping them: activation would land in late February or early March. Adopting different specifications at that point would push mainnet to April or May, because client teams need time to implement and test whatever is agreed.

Client teams are split on whether to absorb that risk. Geth, Nethermind, Reth and ethrex backed proceeding with the current rules. Erigon preferred modifications. Besu raised reservations but indicated it could go ahead with the existing approach.

Researcher Toni Wahrstätter argued for caution about changing the design late. “Every spec change could, again, break new invariants that we are not aware of breaking yet,” he said during the discussion.

The practical effect falls on teams that had planned around a December fork. Wallet, bridge and lending protocols that must reprice or redeploy contracts now have a window measured in months and no fixed date to build toward, only a decision point in January and a mainnet target that depends on it.

Share this article

Viber uses viber://forward?text= when the app is installed.