Skip to content
Basis Desk

New from Basis Desk: free Telegram proxies for places where Telegram is blocked or slowed down.Connect in one tap →

Tech & Protocols · 2 min read

Ethereum Delays Glamsterdam Upgrade on Hoodi Testnet Over Smart Contract Vulnerabilities

Core developers postponed the Oct. 26 activation after auditors found that gas pricing changes would break invariants relied upon by certain projects.

Editorial oversight: Julian Mercer, Chief Editor
Neutral

At a glance

What happened
Ethereum core developers delayed the Glamsterdam upgrade on the Hoodi testnet, which was scheduled for Oct. 26.
Why it matters
The upgrade's gas pricing changes break invariants relied upon by certain smart contracts, exposing them to potential vulnerabilities.
Who is affected
Ethereum developers, Hoodi testnet node operators, and smart contract creators.
What's next
A new activation schedule for the Hoodi testnet will be announced at a later date.
Primary source
Ethereum Foundation Blog: EIP-8037/EIP-8038 Glamsterdam

Key points

  • Ethereum delayed the Glamsterdam upgrade on Hoodi after auditors found gas pricing changes would break smart contract invariants.
  • The Oct. 26 activation at epoch 132,352 has been canceled, and no new date has been set.
  • Node operators must update their software to versions that do not include the scheduled Hoodi activation.

Ethereum core developers have canceled the scheduled activation of the Glamsterdam upgrade on the Hoodi testnet, which was previously slated for Oct. 26, 2026. The delay follows findings that the upgrade's changes to gas pricing would break invariants relied upon by some smart contracts, exposing them to vulnerabilities 1.

Vulnerabilities Discovered by Chainsecurity

The delay stems from issues identified by Chainsecurity, which found that certain projects rely on invariants that are broken by EIP-8037 and EIP-8038 1. These EIPs rework how gas is charged for state creation and access operations 1. Based on the discoveries, the All Core Developers (ACD) group decided to postpone the Hoodi hardfork until a resolution can be reached 1. To facilitate a pragmatic decision, the Ethereum Foundation is engaging multiple auditing firms and conducting internal reviews 1. A public repository detailing the eight broken invariants has been created to help contract developers verify if their projects are affected 1.

Hoodi Configuration Reverted

The previously scheduled activation on Hoodi at epoch 132,352 is no longer planned, and a replacement date has not been set 2. Core developers decided on ACDE #248 to delay the upgrade to allow for further investigation into how EIP-8037 interacts with mainnet smart contracts 2. This delay removes both the Amsterdam execution layer activation and the Gloas consensus layer activation, as well as a gas-limit schedule that would have raised Hoodi's gas limit to 200M 2. Node and validator operators are advised to update their clients to software versions that reflect the postponed activation 2.

Glamsterdam Upgrade Details

Glamsterdam is a major upgrade that combines the Amsterdam execution layer and the Gloas consensus layer 3. Its primary features are enshrined proposer-builder separation (ePBS) under EIP-7732 and block-level access lists (BALs) under EIP-7928 3. ePBS aims to reduce reliance on trusted middleware by bringing the separation of block proposers and builders into the consensus protocol 3. BALs are designed to allow clients to parallelize state reading and transaction validation, improving efficiency 3.

In addition to these changes, the upgrade includes significant adjustments to gas accounting. EIP-8037 increases the cost of creating state, while EIP-8038 updates the cost of state access 3. Other changes cover intrinsic transaction gas, calldata, and block gas accounting 3. Application developers have been advised to test their contracts against these new rules, especially those relying on fixed gas stipends or assumptions about remaining gas 3.

Client Software Updates

Several client teams have released updates to unschedule the Hoodi fork. For example, Besu released version 26.10.1, which reverts the scheduling of Amsterdam on Hoodi 6. The eth-clients/hoodi repository removed amsterdamTime from Hoodi's genesis file, moving the GLOAS_FORK_EPOCH to infinity 7. Lodestar and ethrex also merged pull requests to align with the unscheduled activation 7. Developers using external block-building infrastructure must follow instructions from their tooling providers 2.

Sources

  1. [1] EIP-8037/EIP-8038 Glamsterdam — Ethereum Foundation Blog, November 6, 2026
  2. [2] Glamsterdam on Hoodi Postponed — Ethereum Foundation Blog, October 22, 2026
  3. [3] Glamsterdam Hoodi Testnet Announcement — Ethereum Foundation Blog, October 16, 2026
  4. [4] Glamsterdam Testnet Announcement — Ethereum Foundation Blog, September 28, 2026
  5. [5] Ethereum Developers Cancel Oct. 26 Glamsterdam Upgrade on Hoodi — thedefiant.io, October 22, 2026
  6. [6] Unschedule Amsterdam on Hoodi by daniellehrner · Pull Request #11709 · besu-eth/besu — github.com, October 22, 2026
  7. [7] chore: unschedule Hoodi Glamsterdam activation by barnabasbusa · Pull Request #33 · eth-clients/hoodi — github.com, October 22, 2026
  8. [8] Alpenglow: What We Learned Running Solana's Biggest Consensus Change — galaxy.com, October 20, 2026

Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.

Community read
How do you read this story for the assets involved? One vote a day, anonymous.
Be the first to vote

The Daily Brief, in your inbox at 07:00 ET

Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.

Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.