Ethereum devs lean to ship Glamsterdam with EIP-8037 unchanged, Hoodi testnet decision delayed
Published
Reported by Unchained · 1 source
News summary · AI-generated summary. No named staff review is recorded for the current text.
What happened
The All Core Devs Execution call leaned toward shipping Glamsterdam with EIP-8037 (raising gas costs for creating accounts, storage slots and contract code) unchanged, but left a decision on forking the Hoodi testnet (proposed for the week of 14 December, realistically 16–17 Dec) until next week. The Ethereum Foundation engaged ChainSecurity and Dedaub , and Rahul Kothari reported at least 50 affected companies; high-impact projects expect fixes by mid-December and many medium-impact projects by 10 January. Most client teams (Geth, Nethermind , Reth, ethrex) favoured scheduling as-is, Besu asked for a spec change and Erigon opposed shipping unchanged. Consensus-layer veto risk and reopened Hegota scope for accelerating post-quantum work were also flagged.
Sources · 1 outlet
About these sources
Outlets may repeat the same announcement. This count is not independent confirmation. How sourcing works.
Event updates
This story is part of a developing event
Developers on the All Core Devs calls generally supported shipping Glamsterdam as written, keeping EIP-8037's repricing of gas for state creation, while deferring a mid-December Hoodi testnet fork decision to next week. Auditors ChainSecurity and Dedaub identified at least 50 affected projects; client teams including Geth, Nethermind, Reth and ethrex mostly backed scheduling, while Besu and Erigon voiced reservations. The Hegota upgrade scope was reopened amid post-quantum security concerns.
Status not recorded · Last material update
Ask about this story
Optional follow-up questions. AI answers can make mistakes; check the sources above.