We checked this claim: is it true that
Ethereum developers proposed technical drafts EIP-8488 and a dual-meter gas structure to fix compatibility flaws in the Glamsterdam upgrade?
software designs remain early drafts under review following the halted October Hoodi rehearsal run
JolinaMarketingComing December 1
Ethereum developers split over upgrade software rewrite
Software engineers weigh dual-meter fees and code versioning after halted trial run threatens older contracts.
In a nutshell
Ethereum software developers halted their next major network upgrade after cybersecurity auditors found that proposed fee changes could disrupt existing automated applications. Engineers are now debating two competing technical solutions: a proposal known as EIP-8488 that runs old and new applications in separate software environments, and an alternative that tracks computational complexity and billing on two separate meters.
Highlights
- Security auditors at ChainSecurity discovered that repricing rules under EIP-8037 threatened existing contract operations.
- Core engineers officially called off the Hoodi testnet upgrade on Oct. 24, 2026, to prevent breaking live applications.
- Technical teams introduced proposal EIP-8488 alongside a dual-meter gas model on Nov. 9, 2026.
- Rescheduling the live Hoodi trial depends on which proposal developers approve during regular technical meetings.
From the Editor’s Diary
When decentralized computer networks lock code permanently onto an immutable ledger, even routine cost adjustments require complex engineering compromises to keep legacy applications running.
Who's involved
Ethereum Core Developers
Engineers maintaining client software programs for the Ethereum network
goal → Fix the fee adjustment flaw without breaking existing programs
ChainSecurity
Independent cybersecurity firm auditing ledger software code
goal → Prevent security risks during network instructions updates
Smart Contract Developers
Software builders running live automated programs on the ledger
goal → Prevent system breaks and expensive rewrites of permanent code
In short
Older decentralized programs across the world's most-used commercial ledger will not be broken by upcoming fee changes, because the technical teams who maintain the network have halted their upgrade roadmap to rebuild its core accounting engine.
The pause makes a delayed launch of Ethereum's Glamsterdam system overhaul the most likely outcome, pending a consensus agreement on client design.
That delay is near-certain because the independent teams writing the system software have not yet scheduled a new dress rehearsal on their trial network, known as Hoodi.
Previously in this story
Ethereum fixes flaw risking user deposits
28 October 2026Core programmers repaired test software that let middlemen seize incoming funds before live launch.Ethereum halts major test run over contract flaw
24 October 2026Developers freeze a planned network overhaul after discovering a pricing error could trap user funds across live applications.Ethereum targets 200 million gas limit in scaling trial
20 October 2026Core developers scheduled the Glamsterdam testnet upgrade for Oct. 26 to test whether higher transaction volume threatens network stability.
How it unfolded
Rehearsal upgrade halted over execution glitch
Security researchers at ChainSecurity found that a plan to reprice technical operations threatened the rules governing live, self-executing software contracts. Client engineers halted a planned test upgrade to draft new protections that would shield older programs from unexpected failures.
Engineering debate splits into two competing software fixes
The test halt pushed technical discussions toward isolating existing programs from incoming network fee rules. Engineers formally introduced proposal EIP-8488 to separate software versions, while putting forward a rival draft that introduces two parallel meters to detach internal computational limits from public transaction fees.
Where things stand
Engineering teams are measuring the added workload and operational complexity of versioned execution against the twin-meter model. Programmers plan to choose between the two models during upcoming All Core Devs technical meetings before rescheduling the Hoodi test run.
