Zimbuck – Your Market. Your Community.

Ethereum Delays Glamsterdam Upgrade: Hoodi Testnet Fork Paused Over Gas Risks

7 min read
0
Comments
350
Views

Ethereum Delays Glamsterdam Upgrade: Hoodi Testnet Fork Paused Over Gas Risks

Ethereum core developers have delayed the Glamsterdam hard fork process and will not fork the Hoodi testnet until smart contract risks tied to EIP-8037 and EIP-8038 are resolved. The Ethereum Foundation confirmed the decision in a blog post on November 6, 2026, after auditor ChainSecurity found that the upgrade's gas changes could break assumptions some deployed contracts rely on.

There is no new date for Hoodi, and mainnet never had a Glamsterdam date. Readers following Ethereum upgrade coverage can track daily developments on the Zimbuck News page.

What Happened: The November 6 Decision

According to the Ethereum Foundation's November 6 blog post, written by developer Marius van der Wijden, the All Core Devs group decided to delay the hard fork process following findings from testing. ChainSecurity had found projects that would be vulnerable after Glamsterdam because they rely on certain invariants — properties contracts expect to stay true — that EIP-8037 and EIP-8038 would break.

The two proposals rework how much gas is charged for certain operations and how gas is charged for state. EIP-8037 changes the cost of creating new blockchain state, while EIP-8038 reprices access to and modification of existing state. Contracts that assume fixed gas costs, or that behave in a specific way when an external call fails, could behave differently — and in some cases unsafely — under the new rules.

The key facts from the Foundation's update are:

  • Decision: All Core Devs delayed the Glamsterdam hard fork process; Hoodi will not be forked until the issues are resolved (Ethereum Foundation, November 6, 2026)
  • Cause: EIP-8037 and EIP-8038 change gas charging for certain operations and state, breaking eight contract invariants documented by the Foundation
  • Source of the finding: auditor ChainSecurity, whose analysis dates to October 13; the Foundation is also working with Dedaub and running internal audits
  • Call to action: contract developers and auditors are asked to check their projects against the eight invariants and report issues to the Foundation
  • Next upgrade: work on Hegota, the upgrade after Glamsterdam, continues in parallel
  • New dates: none given — the decision will be revisited on upcoming All Core Devs calls

Why a Gas Change Can Break Working Contracts

Gas is not just a fee. Many smart contracts are written around precise gas assumptions: a call is given a fixed budget, a failure path is expected to run out of gas and revert, or a safeguard relies on an operation costing exactly what it costs today. When EIP-8037 and EIP-8038 change how gas is charged for state creation and state access, those assumptions can silently stop holding.

ChainSecurity's concern, as described by the Foundation and reported by CoinTelegraph, is that some contracts could become vulnerable precisely at the point where an external call fails — code that was safe under the old gas schedule may continue executing, or fail to execute, in ways its authors never planned for. That is why the Foundation published a repository documenting the eight affected invariants, with explanations and examples, and asked teams across the ecosystem to audit their own code rather than assuming the official review can cover every project and every off-chain system connected to it.

For readers who want the deeper mechanics of how Ethereum upgrades reach finality, our blockchain finality guide explains the process upgrades like Glamsterdam move through before they can safely activate.

Background: Where Glamsterdam Stands

As background, Glamsterdam is Ethereum's next major upgrade. It bundles enshrined proposer-builder separation (EIP-7732) and Block-Level Access Lists (EIP-7928) alongside the gas repricing work now under review. The upgrade went live on the Sepolia testnet on October 6, and Hoodi — the final major rehearsal before any mainnet decision — had been tentatively lined up for late October before this delay sequence began.

The important point for holders is what did not happen: nothing changed on mainnet. No action is required from ETH holders, node operators outside the testnet process, or ordinary users. The delay is a testnet-stage safety pause, taken specifically so that a compatibility problem is fixed before it can ever reach live contracts and real funds.

Members weighing what a slower upgrade timeline means for Ethereum's roadmap are discussing the decision in the Zimbuck Market News group.

ETH Price: Flat While Developers Pause

The market reaction was muted. ETH traded near $2,232 on November 7 — reported at about $2,232 at around 17:20 UTC using CoinMarketCap data, roughly flat over 24 hours and down about 0.80% over seven days — while Basis Desk's November 7 close put ETH at $2,236, down 0.1% on the day.

Those two figures are not a contradiction: they are snapshots taken at different times by different providers, and both describe the same picture — ETH holding in the low $2,200s with no sharp move on the delay news. A testnet pause, with mainnet untouched and no funds at risk, is the kind of headline traders tend to treat as a roadmap story rather than a market event. That calm also contrasts with the pressure visible in recent Ethereum ETF outflows covered on Zimbuck, which have moved sentiment more than protocol scheduling news has.

What Happens Next

The Foundation's next steps are audit-driven, not calendar-driven. ChainSecurity and Dedaub are engaged, internal audits are running, and project teams are reporting against the eight invariants. Based on that feedback, developers may adjust the specifications of EIP-8037 and EIP-8038 themselves before Glamsterdam proceeds — the November 6 post leaves that door explicitly open.

Meanwhile, work on Hegota continues in parallel, so the delay does not freeze Ethereum's wider roadmap. The Glamsterdam timeline will be revisited on the next All Core Devs calls, and until those calls produce a decision, any specific new Hoodi or mainnet date would be speculation. The honest summary is simple: Ethereum chose contract safety over schedule, and the cost of that choice is time, not security.

Frequently Asked Questions

Why did Ethereum delay the Glamsterdam upgrade?

In its November 6, 2026 blog post, the Ethereum Foundation said All Core Devs decided to delay the Glamsterdam hard fork process after ChainSecurity found that EIP-8037 and EIP-8038 — which change how gas is charged for certain operations and for state — would break invariants some existing contracts rely on, leaving some projects vulnerable.

What happens to the Hoodi testnet fork?

Hoodi will not be forked until the issues are resolved. The Foundation gave no new date; the decision will be revisited on upcoming All Core Devs calls. Glamsterdam had already gone live on the Sepolia testnet on October 6.

Does the Glamsterdam delay affect ETH holders or mainnet?

No. The delay is at testnet stage, mainnet never had a Glamsterdam activation date, and no action is required from ETH holders. Work on the following upgrade, Hegota, continues in parallel.

How did ETH trade after the delay news?

ETH was near $2,232 on November 7 (about 17:20 UTC, CoinMarketCap data, roughly flat over 24 hours, down about 0.80% over seven days), while Basis Desk's November 7 close was $2,236, down 0.1% — different snapshots, the same flat picture.

Join the conversation and follow the latest Ethereum and crypto market coverage at zimbuck.com.

This article is market news and general information only, not financial advice.