--- title: "Ethereum Core Developers Postpone Glamsterdam Upgrade on Hoodi Testnet" description: "Engineers delayed the scheduled Oct. 26 deployment to examine how EIP-8037 interacts with mainnet smart contracts, leaving a new activation epoch unset." url: https://basisdesk.news/news/ethereum-delays-glamsterdam-upgrade-hoodi-testnet published: 2026-10-23T01:41:15.858Z modified: 2026-10-23T01:41:15.858Z section: Ethereum & L2s author: Basis Desk Newsroom (AI-generated, source-verified) sentiment: neutral tickers: [ETH] tags: [glamsterdam, hoodi-testnet, core-devs, eip-8037, client-upgrades] license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice. --- # Ethereum Core Developers Postpone Glamsterdam Upgrade on Hoodi Testnet Engineers delayed the scheduled Oct. 26 deployment to examine how EIP-8037 interacts with mainnet smart contracts, leaving a new activation epoch unset. ## At a glance - **What happened:** Ethereum core developers postponed the Glamsterdam upgrade on the Hoodi testnet originally set for Oct. 26, 2026. - **Why it matters:** The delay allows developers to probe how EIP-8037 interacts with mainnet smart contracts before executing network state changes. - **Who is affected:** Hoodi testnet node operators, validators, client teams, and decentralized application developers. - **Takes effect:** 2026-10-26 - **What's next:** Core developers will publish a revised activation schedule at a later date once client configurations and contract checks are resolved. - **Status:** announced - **Primary source:** [Glamsterdam on Hoodi Postponed](https://blog.ethereum.org/en/2026/10/22/glamsterdam-hoodi-delay) — Ethereum Foundation Blog ## Key points - Core developers agreed during ACDE #248 to postpone the Oct. 26 Glamsterdam upgrade on the Hoodi testnet. - The delay stems from the need to investigate potential interactions between EIP-8037 and mainnet smart contracts. - Hoodi node and validator operators must update client software prior to Oct. 26 to remove the previous activation parameters. ## Editorial remark - **Context:** The Glamsterdam hard fork couples the Amsterdam execution layer with the Gloas consensus layer, marking a primary testnet milestone on Hoodi ahead of any eventual mainnet deployment. - **Impact:** Hoodi node operators, validators, and infrastructure builders must update client software to remove the hard fork trigger before Oct. 26, while mainnet users remain unaffected. - **Watch:** Ethereum core developers are set to announce a revised Hoodi activation schedule and provide further findings regarding EIP-8037 contract compatibility. Ethereum core developers have officially postponed the Glamsterdam network upgrade on the Hoodi testnet, which was previously slated to execute on Oct. 26, 2026, at 17:42:48 UTC (epoch 132,352) [1]. According to an announcement from the Ethereum Foundation, participants decided during All Core Devs Execution call #248 to delay the testnet deployment to allow for deeper analysis of how Ethereum Improvement Proposal 8037 interacts with existing mainnet smart contracts [1]. At the time of writing, $ETH traded at $2,381, down 3.6% over the past 24 hours amid broader market softness. The postponement cancels the scheduled activation of the Amsterdam execution layer and the Gloas consensus layer on Hoodi [1]. In addition, the decision withdraws an associated configuration that would have expanded the Hoodi testnet's gas limit to 200 million units at the target epoch [1]. The Ethereum Foundation clarified that the adjustment simply rolls back future upgrade configurations rather than reverting any transaction history on the Hoodi testnet [1]. No replacement activation timestamp or epoch has been established yet [1]. ## Client Updates and Testing Guidance Node operators and validators running infrastructure on Hoodi must update both their execution-layer and consensus-layer clients prior to Oct. 26 [1]. Client teams have started publishing revised builds that cancel the hard fork trigger; the Ethereum Foundation confirmed that Lodestar v1.50.1, Besu 26.10.1, Ethrex v30.0.1-rc.2, and Nethermind 2.2.1 include the updated testnet schedule [1]. Operators utilizing external block-builder tooling or custom network settings must also align configurations to avoid maintaining the discarded activation epoch [1]. The schedule change supersedes previous deployment plans, following earlier notices where [client teams unscheduled the upgrade](https://basisdesk.news/news/ethereum-clients-unschedule-hoodi-glamsterdam-upgrade) across various repositories [1]. Application developers have been advised to halt test plans premised on the Oct. 26 activation date until a replacement timeline is published [1]. The delay applies exclusively to the Hoodi testnet environment; it establishes no mainnet schedule, and mainnet users and asset holders need not take action [1]. ## Sources 1. [Glamsterdam on Hoodi Postponed](https://blog.ethereum.org/en/2026/10/22/glamsterdam-hoodi-delay) — Ethereum Foundation Blog, 2026-10-22 --- Basis Desk Newsroom · AI-generated, source-verified · https://basisdesk.news/about/how-we-use-ai