BREAKING
US Senate Passes DEATH BETS Act to Ban Prediction Markets on War, Terrorism, and Assassination ● Bitcoin Dips Below $60,000 Amid Broader Technology and AI Stock Selloff ● Sky Protocol Weathers $2 Billion Redemption Wave Amid Scrutiny Over Illicit Transactions ● Wrapped Monero (XMR1) Plunges Over 99% on Hyperliquid After Suspected Infrastructure Breach and $13.5M Selloff ● Coinbase Prepares to Launch In-House Prediction Markets by 2027 Following Major CFTC Regulatory Milestones ● The Rise of the Techno-Compute Class: Why Hardware Mastery is the Definitive Skill of the Coming Decade ● Vercel Resolves OpenTelemetry Blind Spot in AI SDK With New Inference Duration Histogram ● YBUSDT Approaches Potential Turning Point Amid Signs of Returning Buying Interest ●
Ethereum Ecosystem

Ethereum Core Developers Delay Hoodi Upgrade as Gas Repricing Proposals Threaten Existing Smart Contracts

Photo: Documentation / News Illustration

Ethereum developers have hit the pause button on the hard fork process for the upcoming "Glamsterdam" network upgrade. The decision comes after security audits revealed that proposed adjustments to gas mechanics could invalidate crucial security assumptions relied upon by existing decentralized applications.

Glamsterdam, currently undergoing rigorous testing across various Ethereum testnets, introduces significant changes aimed at optimizing network efficiency and state management. Specifically, Ethereum Improvement Proposals EIP-8037 and EIP-8038 are designed to rework how gas is charged for specific operations as well as how state consumption is priced. However, recent testing conducted by blockchain security firm Chainsecurity exposed a hidden vulnerability: these modifications will inadvertently break several underlying invariants that many deployed smart contracts depend on for their core functionality and security.

In response to these findings, AllCoreDevs (ACD) members have made a pragmatic decision to delay the hard fork process. Crucially, the fork will not be deployed to the Hoodi testnet until these compatibility issues are thoroughly investigated and resolved. Meanwhile, development work on the separate "Hegota" upgrade remains entirely unaffected, with parallel engineering efforts continuing at full speed.

To reach an informed and pragmatic consensus during upcoming AllCoreDevs calls, the development community needs a comprehensive understanding of what might break post-Glamsterdam and whether specific specification changes could prevent these vulnerabilities. To tackle this, the Ethereum Foundation has engaged prominent auditing firms Chainsecurity and Dedaub, alongside conducting extensive internal audits. Yet, because the Ethereum ecosystem is vast and decentralized, developers acknowledge that internal and contracted audits cannot possibly cover every single project, especially when accounting for complex combinations of on-chain contracts and off-chain code.

Consequently, core developers have issued an urgent call to action, urging independent smart contract developers, protocol maintainers, and security auditors to audit their own projects against these newly discovered breaking changes. To facilitate this review, the team has established a dedicated GitHub repository outlining the eight core invariants that will be broken by the Glamsterdam upgrade. This repository provides short explanations of the affected invariants, real-world examples, and helpful verification prompts designed to assist developers in testing their own codebases. Developers who discover that their protocols are affected are strongly encouraged to reach out directly to the core team via email.

Update (November 9th, 2026)

In the days following the initial disclosure, momentum has picked up significantly regarding community engagement and developer feedback. Since the initial warning post, the core team has received four distinct reports identifying deployed smart contracts that face potential failure under the gas repricing structures outlined in EIP-8037 and EIP-8038. Core developers have expressed gratitude to community members who submitted examples, noting that every report is actively being reviewed while protocols potentially at risk are being directly contacted.

Alongside these reports, a broader and more fundamental concern has surfaced within the community. Critics and developers alike have argued that any network upgrade modifications impacting already deployed, immutable smart contracts demand a higher level of scrutiny than they are currently receiving. Core developers are taking these concerns very seriously. Current recommendations suggest that the AllCoreDevs group should intentionally delay scheduling the Hoodi upgrade until all upcoming audit findings are fully made public and the community has been given adequate time to review them.

If forthcoming audit data reveals that the negative impact on deployed contracts is too widespread to accept, the AllCoreDevs group is prepared to revise the specifications altogether. In anticipation of this, development work is already underway to prototype and review several possible specification revisions. The core team is currently documenting which specific problems each potential revision would address, as well as tracking which alternative invariants might be broken by these new changes. These findings and revision proposals are scheduled to be formally presented during the AllCoreDevs Execution (ACDE) call on November 19th.

Ahead of these upcoming decisions, the timeline of events remains packed with crucial milestones. Ongoing outreach and triage efforts continue as the core team works directly with potentially affected protocols. On November 12th, the AllCoreDevs Consensus (ACDC) call will convene, though EIP-8037 and EIP-8038 are not currently slated for the agenda. This will be followed shortly by the delivery and publication of the final audit reports from Dedaub and ChainSecurity on November 13th.

To ensure complete transparency, an AllCoreDevs Testing (ACDT) call is scheduled for November 16th, where Dedaub, ChainSecurity, and the Ethereum Foundation will present their comprehensive findings. This session will feature an open Q&A period, and application developers are strongly encouraged to attend. Finally, the ACDE meeting on November 19th will serve as the primary forum for discussing the findings and determining the next steps, with developers emphasizing that no final decisions have been pre-committed.

Developers who believe their protocols might be affected are advised to review the invariants repository and reach out to the core team via email. Publicly disclosed reports are also being closely monitored by the triage team as the network prepares for its next critical evaluation phase.

What is your reaction to this story?

Nila Kartika Wati

Writer and contributor at Bitcoin 98.

Comments (0)