Ethereum

Ethereum developers debate EIP-8037 gas repricing for Glamsterdam

Ethereum core developers face technical disagreements over EIP-8037 gas repricing, which increases costs for creating state elements. Auditors ChainSecurity and Dedaub identified 50 companies affected by the changes, leading to discussions about a potential mid-January 2027 mainnet date.

Ethereum developers debate EIP-8037 gas repricing for Glamsterdam

EIP-8037 gas repricing disagreements

Ethereum core developers favor shipping the Glamsterdam hard fork with the current EIP-8037 gas repricing specification. The proposal increases gas costs for creating new state elements like accounts, storage slots, and contract code. Auditors ChainSecurity and Dedaub identified 50 companies affected by these changes. Rahul Kothari, the Ethereum Foundation Dev Tooling Lead, suggested mid-January 2027 as the earliest mainnet date because high-impact projects must fix their contracts by mid-December. Medium-impact projects expect to be ready between next week and Jan 10.

The technical disagreement remains sharp between client teams. Besu developer Justin Florentine argued that "changing the gas accounting and breaking things like try catch and Solidity is more concerning" than breaking contracts that hard-code gas prices. Marius van der Wijden from Geth noted that the alternative of moving gas refunds to the end of a transaction is also expensive. Under the current EIP-8037 rules, a transaction can make about 160 state writes within a 16 million per-transaction gas cap, meaning callers would need to massively increase the amount of gas they send to ensure the transaction succeeds. Most client teams, including Geth, Nethermind, Reth, and ethrex, favor scheduling the fork now, though Erigon developer Andrew Ashikhmin spoke against shipping the upgrade in its current form.

Project Impact Level Readiness Deadline
High-impact Mid-December
Medium-impact Next week to Jan 10

Hoodi scheduling and Hegota scope

Ansgar Dietrichs, an EIP-8037 co-author, proposed aiming for a Hoodi testnet fork during the week of Dec 14, specifically Dec 16 or 17. This proposal leaves the final decision to the All Core Devs Consensus (ACDC) call scheduled for next week. Developers previously scrapped an Oct 26 Hoodi date after ChainSecurity flagged gas risks. Ben Edgington warned of a "consensus breaking change on the consensus layer" that might get vetoed next week. Dietrichs invited anyone still pushing for a change to hold a bit of a mini sprint before next week to bring a concrete proposal. Forking Hoodi this year would commit Glamsterdam to its current specification.

Dietrichs also reopened the scope of the Hegota upgrade to accelerate post-quantum security timelines. He presented five options for the upgrade, ranging from a normal fork of 10 to 15 EIPs to dropping frames for a built-in post-quantum transaction type. The last option received absolutely zero support from the developers. Client teams must submit short written positions by the end of next week to allow for discussion in two weeks. New EIPs stay off the execution-layer development network by default, and a cross-layer test network waits on the consensus developers’ call on Fork-Choice Enforced Inclusion Lists (FOCIL).