Ethereum Developers Lean Toward Shipping Glamsterdam Unchanged, Hoodi Testnet Decision Moves to Next Week
Crypto Gas Fee Calculator
Ethereum's core developers leaned toward shipping the network's next upgrade, called Glamsterdam, with its contested gas repricing left unchanged, according to reporting on Thursday's All Core Devs Execution call. They held off on a final decision about a mid-December testnet fork until next week.
The change at the center of the debate is Ethereum Improvement Proposal (EIP) 8037. It raises the gas cost of creating new state on the network, such as new accounts, storage slots, and contract code. Gas is the fee paid to run transactions on Ethereum.
Key points from the call
- Most client teams favored scheduling a Hoodi testnet fork for the week of Dec. 14, realistically Dec. 16 or 17, with the formal decision set for next week's consensus call.
- The Ethereum Foundation brought in auditors ChainSecurity and Dedaub to test which deployed contracts the repricing could break. They had reached at least 50 affected companies, according to Foundation Dev Tooling Lead Rahul Kothari.
- Kothari suggested mid-January as the earliest mainnet date. All three projects rated high impact have fixed or will fix their contracts by mid-December, and medium-impact projects expect readiness between next week and Jan. 10.
- Besu still wants the specification changed, and consensus-layer developers could veto the proposed testnet date.
What developers said on the call
Ansgar Dietrichs, Ethlabs co-founder and a co-author of EIP-8037, moderated the call. He proposed forking Hoodi, a public test network, in the week of Dec. 14, with the decision made on next week's All Core Devs Consensus call. Developers had scrapped an earlier Hoodi date of Oct. 26 after ChainSecurity flagged gas risks. Forging ahead this year would lock in the current version of EIP-8037. Dietrichs invited anyone still seeking a change to run what he called "a bit of a mini sprint between now and next week" and return with a concrete proposal. He said he did not necessarily see enthusiasm for the compromise, but no one spoke up to veto it.
Most client teams, the groups that build the competing software that runs Ethereum's nodes, supported scheduling. Marius van der Wijden backed penciling in Hoodi for Geth. Nethermind said it was fine scheduling. Reth's Dragan Rakita voiced support, and ethrex's Iván said he favored "scheduling now, and no spec changes."
Besu, which had asked on GitHub before the call to delay the fork for a narrow fix or move EIP-8037 to the following upgrade, went along with the group. Its Justin Florentine had argued that changing gas accounting and breaking features like try catch and Solidity is more concerning than breaking contracts that hard-code gas prices. "We still think that we should change the spec," he said, adding that it "doesn't seem like anybody else does." Erigon's Andrew Ashikhmin spoke against shipping as is.
Van der Wijden also noted that the most-favored alternative, moving gas refunds to the end of a transaction, carries its own costs. Under EIP-8037 as written, a transaction can make about 160 state writes within a 16 million per-transaction gas cap, he said. Without refunds inside the transaction, callers would need to send much more gas. Even that fix, he said, has "significant drawbacks that we don't fully understand yet."
The date could still slip from the consensus layer, the half of Ethereum that runs proof-of-stake. Ben Edgington, speaking for that side, flagged a consensus breaking change and warned that whatever was decided on the execution call might get vetoed next week.
What is confirmed and what is not
Confirmed from the call: developers leaned toward shipping Glamsterdam as written, most client teams supported scheduling a Hoodi fork for the week of Dec. 14, the auditors had contacted at least 50 affected companies, and the formal go or no-go decision was deferred one week. The earlier Oct. 26 testnet date was scrapped after ChainSecurity flagged gas risks.
Still open: whether the Hoodi fork actually happens on that date, since consensus-layer developers could veto it, and whether any spec change to EIP-8037 emerges from the coming week. Besu's preference for a spec change did not have broad support on the call.
Hegota scope reopened
Developers also reopened the scope of Hegota, the upgrade planned after Glamsterdam. Concerns about post-quantum security fueled a desire to accelerate those timelines, Dietrichs said. His slide listed five options, ranging from a normal fork with 10 to 15 of roughly 20 candidate EIPs, to a smaller fork with fewer than 10, to shipping just the core bundle or core EIP for frame transactions, the planned post-quantum platform, to dropping frames in favor of a built-in post-quantum transaction type. The last option drew what Dietrichs described as absolutely zero support.
Client teams owe short written positions by the end of next week, for discussion in two weeks. Until then, new EIPs stay off the execution-layer development network by default. A cross-layer test network waits on the consensus developers' decision on Fork-Choice Enforced Inclusion Lists (FOCIL), that layer's Hegota headliner.
Why the timing matters
Dietrichs estimated that agreeing on any alternative spec would take a week or two, plus about four weeks of impact analysis, which would run past the Hoodi window. Forging Hoodi this year keeps EIP-8037 as written. Waiting for the analysis would push mainnet to late February or early March at the earliest by his estimate, or April or May if changes are made. These figures are his estimates, not confirmed dates.
Crypto Gas Fee Calculator
What happens next
Next week's All Core Devs Consensus call is set to decide on the mid-December Hoodi testnet fork. Client teams must also submit written positions on Hegota's scope by the end of next week, with discussion to follow in two weeks.