Ethereum devs line up behind EIP-8037—Hoodi fork vote delayed, veto threat next

0

Ethereum core developers leaned toward shipping the Glamsterdam hard fork with its disputed gas repricing unchanged, while pushing a final decision on a mid-December Hoodi testnet fork to next week, according to Unchained’s readout of Thursday’s All Core Devs Execution (ACDE) call.

What’s at stake: EIP-8037’s gas repricing

At the center is EIP-8037, which raises the gas cost of creating new state (accounts, storage slots, contract code). Unchained reported that the Ethereum Foundation engaged ChainSecurity and Dedaub to test which deployed contracts could break. EF Dev Tooling Lead Rahul Kothari told the call that at least 50 companies had been contacted. He suggested mainnet would be no earlier than mid-January, saying high-impact projects had fixed or would fix by mid-December, and most medium-impact projects expected readiness between next week and Jan. 10.

Hoodi timing slips to next week’s vote

EIP-8037 co-author and call moderator Ansgar Dietrichs floated forking the Hoodi testnet in the week of Dec. 14—realistically Dec. 16 or 17—pending next week’s All Core Devs Consensus (ACDC) call, Unchained reported. Developers had previously scrapped an Oct. 26 Hoodi date after ChainSecurity flagged gas risks. Dietrichs said forking Hoodi this year would effectively commit Glamsterdam to the current spec unless a concrete alternative emerges immediately.

Client teams mostly favor scheduling—split views on spec changes

Unchained’s account of the call cites broad support among execution clients for penciling in Hoodi: Geth developer Marius van der Wijden backed scheduling; Nethermind was fine with it; Reth’s Dragan Rakita voiced support; and ethrex’s Iván supported “scheduling now, and no spec changes.”

Besu had asked on GitHub to delay the fork for a narrow fix or move EIP-8037 to a later upgrade, per Unchained. On the call, Besu’s Justin Florentine said, “We still think that we should change the spec,” arguing that “changing the gas accounting and breaking things like try catch and Solidity is more concerning” than breaking contracts that hard‑code gas prices. Erigon’s Andrew Ashikhmin spoke against shipping as is.

The fix that isn’t simple

Van der Wijden said the leading alternative—moving gas refunds to the end of a transaction—would also be costly. 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 massively increase the amount of gas,” and even that approach has “significant drawbacks that we don’t fully understand yet,” according to Unchained.

Consensus layer may veto

Ben Edgington, speaking for consensus-layer developers, warned of “a consensus breaking change on the consensus layer” and said “whatever we decide today, it might get vetoed” next week, Unchained reported.

Next up: Hegota scope reopens amid PQ concerns

Dietrichs said the scope of Hegota—the upgrade after Glamsterdam—was reopened to potentially accelerate post‑quantum timelines, per Unchained. Five options were listed, ranging from a normal fork (10–15 of ~20 EIPs) to a minimal set centered on “frame transactions,” with “absolutely zero support” for replacing frames with a built‑in post‑quantum transaction type. Client teams owe short written positions by the end of next week, and new EIPs remain off the execution-layer devnet by default. A cross‑layer testnet waits on consensus developers’ call on Fork‑Choice Enforced Inclusion Lists (FOCIL), according to Unchained.

The calendar math

Unchained reported Dietrichs’s estimate that agreeing on an alternative spec would take one to two weeks, plus roughly four weeks for impact analysis—pushing past the Hoodi window. Forking Hoodi this year would keep EIP‑8037 as written; waiting for analysis would push mainnet to late February or early March at the earliest, or April or May if changes are adopted.

You might also like
Leave A Reply

Your email address will not be published.

You have not selected any currency to display
Powered by Reach Response