News analysis ·
Ethereum upgrade date: Hoodi call could lock Glamsterdam
Ethereum developers lean toward shipping Glamsterdam with EIP-8037 unchanged. We explain why a Hoodi testnet fork would fix the spec and the timeline.

Ethereum core developers leaned toward shipping the Glamsterdam hard fork with its disputed gas repricing, EIP-8037, left as it is, Unchained reported after the Thursday execution-layer developer call, known as ACDE. The yes or no on a mid-December fork of the Hoodi testnet moved to next week. This article looks at why that testnet date is really a decision about the spec, and who carries the cost either way.
The change in one paragraph
EIP-8037 makes it more expensive, in gas, to create new state on Ethereum. State is the network's shared memory: account balances, the storage slots that smart contracts write to, and deployed contract code. According to Unchained, most client teams now want to schedule the fork without changing that rule, while a minority still wants a different design.
Under the hood: what a gas repricing touches
Gas is the unit Ethereum uses to meter work. Every operation has a price in gas, and every transaction carries a gas limit set by the sender. When a protocol upgrade changes those prices, any contract that assumed the old numbers can stop working as intended.
- State creation: EIP-8037 raises its gas price, which is the core of the change.
- Per-transaction cap: the current text lets one transaction perform roughly 160 state writes before hitting a 16 million gas ceiling per transaction, Geth developer Marius van der Wijden said.
- Refunds: the leading alternative design would pay out refunds only once the transaction finishes.
- Hard-coded gas: some deployed contracts pass a fixed amount of gas to other calls, so a price rise can leave those calls short.
The refund question shows why there is no free fix. Van der Wijden said the refund alternative carries its own costs. Besu’s Justin Florentine argued that changing gas accounting and breaking try catch patterns and Solidity worried him more than breaking contracts with hard-coded gas prices. So the trade-off, in his telling, is between contracts that may break and accounting rules that may behave in new ways.
When is the Ethereum upgrade date, and why does Hoodi decide it?
A testnet fork is a dress rehearsal. Client software ships with the new rules, a public test network switches over, and the spec is effectively frozen from that point. Unchained noted that forking Hoodi this year would lock Glamsterdam into its present spec. So next week's vote is less about a calendar slot and more about whether EIP-8037 stays as written.
Ansgar Dietrichs, Ethlabs co-founder, EIP-8037 co-author and the call's moderator, proposed forking Hoodi in the week of Dec. 14, most likely Dec. 16 or 17. An earlier Hoodi date, Oct. 26, was dropped after the auditor ChainSecurity raised gas risks. On the mainnet side, Rahul Kothari, who leads dev tooling at the Ethereum Foundation, named mid-January as the earliest date.
Dietrichs also laid out the cost of changing course. By his estimate, agreeing on an alternative takes a week or two, and then about four weeks of impact analysis would follow. That sequence does not fit before the Hoodi window closes. If developers chose to wait, the mainnet fork would land no sooner than late February or early March, or April or May if the spec changes.
Who is affected
Smart contract teams are first in line. The Ethereum Foundation hired auditors ChainSecurity and Dedaub to find which live contracts the repricing might break. Kothari said outreach covered at least 50 companies hit by the change. In his account, the three projects judged high impact have already patched, or will patch, before mid-December, while medium-impact teams put their readiness somewhere from next week to Jan. 10.
Client teams, which build the competing node software, are the second group. Geth, Nethermind, Reth and ethrex supported scheduling the fork, with ethrex backing scheduling and no spec changes. Besu had asked for a delay or for EIP-8037 to move to a later upgrade, but went along. Erigon's Andrew Ashikhmin opposed shipping unchanged. Dietrichs, the call’s moderator, said: "I didn’t necessarily see enthusiasm".
Ordinary users mostly feel this through apps: a contract that has not been updated could fail after the fork.
Status and next steps
The final Hoodi call sits with next week's consensus-layer developer call, ACDC. A delay could also come from that side of the network, which runs proof of stake. Ben Edgington, representing consensus developers, raised a consensus breaking change there and cautioned that the decision could be vetoed next week.
Hegota, the fork planned after Glamsterdam, is open for debate again, as post-quantum security concerns pushed for faster timelines. Dietrichs showed five options, from a normal fork taking 10 to 15 of the roughly 20 candidate EIPs down to only frame transactions. Each client team owes a brief written stance before next week is out, with discussion in two weeks.
Sources
- Unchained, 20 Nov 2026
AI wrote this summary from the primary documents and reports cited above. It went live automatically after checks that figures match those sources and nothing is copied; there was no human review. It explains a protocol or rule change and is not investment advice.