Ethereum Glamsterdam Upgrade Delayed: Security Risks Found — What the Hoodi Testnet Postponement Means for ETH Price

What Happened: Glamsterdam's Oct. 26 Testnet Activation Is Off

On October 22, Ethereum developers officially postponed the activation of the Glamsterdam upgrade on the Hoodi test network. The fork had been scheduled to go live on Hoodi on October 26 — the final public testnet rehearsal before developers could pick a mainnet date for one of Ethereum's most ambitious upgrades in years.

The postponement was confirmed at the Oct. 22 All Core Developers Execution meeting. Ethereum Foundation leadership concluded that the upgrade could not proceed as planned after blockchain security firm ChainSecurity identified potential vulnerabilities affecting existing smart contracts. As research-firm founder Christine Kim (Protocol Watch) first disclosed on X, the cancellation was "due to security issues found in" Glamsterdam — and Hoodi node operators were advised to revert to older software versions or install updated execution clients that remove the scheduled activation.

The Ethereum Foundation did not name the affected projects, provide contract addresses, or give an alternative fork date. What it did do was assess the scope of the impact — a process that is still ongoing.

How the Gas Proposals Fit Into Glamsterdam's Bigger Picture

To understand why EIP-8037 and EIP-8038 exist at all, it helps to see what Glamsterdam is trying to achieve. Ethereum's developers have been working for years on a long-term roadmap: cheaper transactions, faster finality, and the ability to validate blocks in parallel rather than one transaction at a time.

The flagship feature of Glamsterdam is ePBS — enshrined proposer-builder separation — which moves the block-building auction into Ethereum's core protocol instead of relying on external relay infrastructure. Alongside it come block-level access lists (BALs), which let validators know in advance which parts of the state each transaction will touch, enabling parallel execution. Together, these changes lay the groundwork for the dramatically higher throughput Ethereum will need as on-chain activity grows.

The gas proposals that caused the delay are part of the same efficiency drive. Today's gas accounting was designed when the network was far simpler; state creation and state access costs don't cleanly reflect the real computational burden they impose on clients. EIP-8037's separate gas reserve for state creation is meant to make that accounting fairer and more predictable — and to unlock larger blocks (like the 200-million gas-limit experiment on Hoodi) without breaking client performance.

In other words, the idea behind the change is sound; the problem is in the interaction with existing contracts that were written under the old assumptions. This is the hardest class of bug in blockchain development: a change that is perfectly correct for all new code but subtly alters the behavior of contracts that are already deployed and immutable. Ethereum's history is full of such traps — which is exactly why the network runs three public testnets before any hard fork touches mainnet.

The Technical Issue: EIP-8037 and EIP-8038 Gas-Accounting Changes

The security concern centers on two Glamsterdam proposals — EIP-8037 and EIP-8038 — that change how Ethereum charges gas for creating and accessing blockchain state. EIP-8037 introduces a separate gas reserve for creating new state (a "state-gas reservoir"), while EIP-8038 changes the cost of accessing and modifying existing state.

In an October 13 report, ChainSecurity warned that these changes could undermine safeguards that existing applications use to distinguish failed transactions from operations that should remain eligible for another attempt. The mechanism is subtle but dangerous: under the proposed rules, code handling a failed external call could behave differently after the upgrade even if nobody edits the contract. "Even with unchanged contract code, a failure path that previously reverted can now complete," the firm wrote — and continuing in that situation "can turn a retryable operation into a permanent failure."

Concretely, a caller could deliberately provide insufficient gas to complete a target operation but enough for the outer contract to record a permanent failure — eliminating the recovery path for operations that were previously retryable. DeFi applications that manage withdrawals, batched transactions, and automated failure recovery are the most exposed.

ChainSecurity says it has already found 13 real-world examples of vulnerable deployed applications and is conducting responsible disclosure with the affected projects. The firm urged all developers to review their contracts immediately. A day before the Oct. 22 developer call, security researcher pcaversaccio asked developers on GitHub to discuss the findings, writing that "these findings call for a reassessment of this hard fork."

Understanding what went wrong requires understanding how smart contracts handle gas — our complete guide to smart contracts breaks down execution, gas, and why contract behavior depends on the exact rules of the network they run on.

Why the Delay Matters: The December Mainnet Timeline Is Now in Doubt

The Hoodi activation was never just a testnet formality. Before the cancellation, the Oct. 22 developer agenda said teams aimed to select a mainnet date at the following week's consensus call if Hoodi went smoothly. With Hoodi off the table, the network's next hard fork has no final public test date — and without it, the trigger for picking a mainnet date.

Glamsterdam's scope makes the delay more than a scheduling hiccup. The upgrade bundles proposer-builder separation into Ethereum's protocol, block-level access lists (BALs) for parallel validation, and a planned increase in Hoodi's gas limit to 200 million — designed to test Ethereum's ability to handle substantially larger transaction volumes. That gas-limit increase is now suspended too.

For context, the upgrade had already activated on Sepolia on October 6, and the Oct. 26 Hoodi date was meant to be the final dress rehearsal. Analysts had penciled in an early-December mainnet target. That timeline is now officially uncertain — the Ethereum Foundation's impact assessment will determine how quickly developers can ship a fix or redesign the gas proposals, and whether the rest of the upgrade can proceed on schedule.

History suggests caution pays: Ethereum's developer culture has repeatedly preferred delays over rushed forks, and the ecosystem's trillion-dollar market cap arguably depends on that discipline.

Market Reaction: ETH Holds Near $2,450 as Traders Digest the Delay

Ethereum traded around $2,464–$2,490 on October 22–23, up roughly 1.5–3.4% on the day, as the broader market rallied behind Bitcoin's push toward $85,000 and a third consecutive day of inflows into U.S. spot Bitcoin ETFs. ETH's resilience is notable: a canceled testnet fork four days before activation is, on paper, bearish for the upgrade narrative — yet the price held firm above the key $2,400–$2,500 zone.

Traders appear to be reading the postponement as a sign of developer seriousness rather than protocol failure. That interpretation has precedent: Ethereum has delayed hard forks before (the Merge's difficulty-bomb delays, the Fusaka scoping debates), and each delay ultimately shipped safely. Meanwhile, the full explainer on Glamsterdam's ePBS and block-level access lists shows just how technically aggressive this upgrade is — scope that makes extra scrutiny a feature, not a bug.

Still, risks remain for ETH bulls. The delay removes the catalyst that several price analyses had pegged as the driver for a $2,500 breakout. With BitMine nearing 5% of the ETH supply and ETF demand returning, the bullish thesis survives — but it now lacks a near-term deadline. A prolonged redesign of EIP-8037/EIP-8038 could push Glamsterdam into 2027, leaving ETH's "upgrade premium" in limbo.

The broader macro backdrop offers both help and pressure: Bitcoin nears $85,000 on ETF flows and FOMC positioning, with prediction markets giving BTC a 20–25% chance of touching $100,000 by year-end (options traders' estimate) — a rising tide that has historically lifted ETH. Our guide on the best time to buy Bitcoin based on history and on-chain data suggests seasonal tailwinds may still be ahead for the whole market.

Expert Views: Praise for Catching It on Testnet

The crypto security community has largely praised the decision. The entire point of the Hoodi rehearsal — and the Sepolia activation before it — is to catch exactly this class of bug before mainnet, and the ChainSecurity finding is a textbook example of testnets working as designed.

"These findings call for a reassessment of this hard fork," wrote researcher pcaversaccio — a measured framing echoed by developers on the Oct. 22 call, who agreed to investigate how EIP-8037 interacts with existing mainnet contracts before setting any new date.

External coverage has been consistent: Unchained, ChainCatcher, Zotpaper and others reported the same core facts — 13 real-world cases, responsible disclosure underway, no alternative date announced. The consistency across independent reports suggests the disclosure process is being handled professionally, not buried.

External coverage: Unchained: Ethereum Scraps Glamsterdam's Hoodi Fork After ChainSecurity Flags Gas Risks; ChainCatcher: Hoodi testnet Glamsterdam hard fork postponed; Zotpaper: postponement details.

Ethereum's Upgrade History: Why Delays Are the Norm, Not the Exception

Skeptics will read "upgrade delayed" as a failure signal. Ethereum's own history tells a different story. The difficulty bomb — the mechanism that forced the network's transition to proof-of-stake — was delayed six times before the Merge finally shipped in September 2022. Each delay was criticized in real time and forgotten in retrospect.

The same pattern played out with the Shanghai/Capella upgrade that enabled staked-ETH withdrawals, and again during the Fusaka scoping debates, where developers repeatedly trimmed and re-trimmed the upgrade's feature list rather than ship a bloated fork. Each time, the market priced the delay as weakness; each time, the eventual clean launch restored the narrative.

There is a structural reason for this conservatism. Ethereum now secures hundreds of billions of dollars in on-chain value, thousands of DeFi protocols, and the settlement layer for a growing share of tokenized real-world assets. A consensus-level bug on mainnet is not a patchable inconvenience — it is an existential threat to the network's credibility. Against that asymmetry, a testnet delay is essentially free insurance.

The ChainSecurity finding also validates a deliberate strategy choice: Ethereum funds independent security research and maintains three public testnets (Hoodi, Sepolia, Holesky's successor) precisely because gas-level changes are impossible to validate purely in theory. The 13 real-world cases the firm found are contracts that passed every prior audit — they only broke under the new execution semantics. No amount of code review on paper would have found them; only running the actual fork on a real testnet could.

For long-term investors, the takeaway is reassuring rather than alarming: the upgrade pipeline caught the problem at the cheapest possible stage. The expensive failure would have been discovering it after mainnet activation.

What Happens Next: Three Scenarios for Glamsterdam

Scenario 1 — Quick fix, minor delay. If the vulnerable patterns are narrowly scoped, developers could adjust EIP-8037's gas-reservoir mechanics and re-test on Hoodi within weeks. Early December mainnet stays theoretically possible but tight.

Scenario 2 — Redesign of the gas proposals. If the interaction with existing contracts is broad, EIP-8037/EIP-8038 may need a fundamental rethink. Glamsterdam could ship without the state-gas changes, or slip into early 2027.

Scenario 3 — Full reassessment. The more systemic the issue, the more likely developers pause the entire Glamsterdam scope and re-scope the fork — the most bearish outcome for near-term ETH sentiment, but the most protective for the network.

The next concrete signal arrives at the following week's consensus call, where developers will assess the Foundation's impact report. Until then, Hoodi stays on the old software, the 200-million gas-limit experiment is shelved, and the 13 disclosed projects race to audit their contracts.

For traders, the key levels remain $2,400 support and $2,500 resistance — a break above the latter on volume, upgrade-delay notwithstanding, would confirm that the market is pricing this as a delay rather than a disaster.

FAQs

Why was the Ethereum Glamsterdam upgrade delayed?

Ethereum developers postponed the Oct. 26 Hoodi testnet activation after ChainSecurity found that proposed gas-accounting changes (EIP-8037 and EIP-8038) could alter the behavior of existing smart contracts — turning retryable failed operations into permanent failures. The Oct. 22 All Core Developers Execution meeting agreed to investigate before setting any new date.

What are EIP-8037 and EIP-8038?

Two Glamsterdam proposals that change how Ethereum charges gas for creating and accessing blockchain state. EIP-8037 introduces a separate gas reserve for state creation; EIP-8038 changes state-access costs. Under the new rules, a contract's failure-handling code could complete where it previously would have reverted from gas exhaustion — which is exactly the behavior ChainSecurity flagged.

Is my ETH or my DeFi position at risk?

No. The issue exists only in the proposed Glamsterdam ruleset, which never activated on mainnet. Ethereum mainnet, Sepolia, and your funds are unaffected. The risk applies to specific contract patterns that the 13 disclosed projects are now reviewing under responsible disclosure.

When will Glamsterdam launch on mainnet now?

There is no new date. The early-December target depended on a smooth Hoodi test, so it is now uncertain. Developers will reassess at the next consensus call after the Ethereum Foundation completes its impact assessment.

Has Ethereum delayed upgrades before?

Yes — repeatedly. The difficulty bomb was delayed multiple times before the Merge, and upgrade scopes are routinely re-scoped at developer calls. Delays for security reasons are a sign of a functioning review process, not a broken protocol.

Does the delay hurt ETH's price?

Short term, it removes a near-term catalyst for the $2,500 breakout and injects timeline uncertainty. Medium term, a safer, well-tested upgrade is better for ETH's institutional narrative than a rushed one. ETH held near $2,450 through the announcement, suggesting traders see a delay, not a disaster.

Conclusion

The Glamsterdam postponement is a reminder of why Ethereum still commands institutional trust: when a top-tier security firm found a real bug, developers pulled the plug four days before a scheduled testnet fork rather than ship and hope. Thirteen vulnerable contract patterns caught on testnet is the system working — even if it costs ETH a near-term catalyst.

The upgrade's core promises — proposer-builder separation, block-level access lists, dramatically higher throughput — are unchanged. What changed is the timeline, and timelines in Ethereum have always been negotiable in the service of safety. Watch the next consensus call for the impact assessment; until then, $2,400–$2,500 is the battleground, and the Hoodi testnet is quietly running the old, safe software.