---
title: "Ethereum Client Teams Unschedule Hoodi Testnet Glamsterdam Upgrade"
description: "Developers revert the planned Oct. 26 activation across client configurations following the ACDE 248 call."
url: https://basisdesk.news/news/ethereum-clients-unschedule-hoodi-glamsterdam-upgrade
published: 2026-10-23T00:26:29.354Z
modified: 2026-10-23T00:26:29.354Z
section: Ethereum & L2s
author: Basis Desk Newsroom (AI-generated, source-verified)
sentiment: neutral
tickers: [ETH]
tags: [ethereum, glamsterdam, hoodi, testnet, besu, lodestar]
license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice.
---

# Ethereum Client Teams Unschedule Hoodi Testnet Glamsterdam Upgrade

Developers revert the planned Oct. 26 activation across client configurations following the ACDE 248 call.

## At a glance

- **What happened:** Ethereum client developers reverted the Hoodi testnet Glamsterdam fork planned for Oct. 26 following ACDE call #248.
- **Why it matters:** The change prevents node divergence across execution and consensus clients on the testnet while retaining configuration presets.
- **Who is affected:** Hoodi testnet validators and node operators running Besu, Lodestar, ethlambda, or ethrex client software.
- **Takes effect:** 2026-10-22
- **What's next:** Core developers will establish a revised activation epoch for the Hoodi Glamsterdam upgrade.
- **Primary source:** [Unschedule Amsterdam on Hoodi by daniellehrner · Pull Request #11709 · besu-eth/besu](https://github.com/besu-eth/besu/pull/11709) — github.com

## Key points

- Core developers canceled the Hoodi Glamsterdam upgrade scheduled for epoch 132352 on Oct. 26 during ACDE call #248 [2].
- Client implementations including Besu, Lodestar, ethlambda, and ethrex reverted fork parameters on Oct. 22 [1][2].
- The rollback removes a planned 200M gas limit raise while keeping Gloas version presets intact for future scheduling [2].

## Editorial remark

- **Context:** The Glamsterdam hard fork was previously slated for deployment on the Hoodi testnet on Oct. 26 before core developers decided to postpone it during ACDE call #248 [2].
- **Impact:** Testnet node operators running Besu, Lodestar, ethrex, or ethlambda must ensure their configurations reflect upstream changes to avoid chain splits [2].
- **Watch:** Core developers must establish a new target activation epoch and release updated client binaries before rescheduling the testnet fork [2].

Ethereum client developers have unscheduled the Glamsterdam network upgrade previously planned for the Hoodi testnet, pulling activation parameters across multiple execution and consensus repositories on Oct. 22 [1][2]. The decision follows an agreement reached during the All Core Developers Execution (ACDE) call #248, calling off the deployment set for epoch 132352 on Oct. 26 [2]. At the time of writing, $ETH traded at $2,382, down 3.8% over the past 24 hours.

The coordinated rollback was initiated upstream in the `eth-clients/hoodi` repository via pull request #33, which stripped `amsterdamTime` from the testnet's genesis file and reverted the `GLOAS_FORK_EPOCH` setting to a far-future value [2]. Client teams moved immediately to integrate the change to prevent nodes from diverging or splitting off from the testnet [2]. Hyperledger Besu developers opened pull request #11709 to unschedule the upgrade, reverting the previous scheduling commit while recording the adjustment under unreleased changes [1]. Simultaneously, client teams for Lodestar, ethlambda, and ethrex updated their respective Hoodi configurations [2].

## Client Configurations Reverted

Beyond reverting the fork epoch, the update removes the experimental `GAS_LIMIT_SCHEDULE` entry that was scheduled to lift Hoodi's gas limit to 200 million gas at epoch 132352 [2]. As reported when [Ethereum developers canceled the Oct. 26 Glamsterdam upgrade on Hoodi testnet](https://basisdesk.news/news/ethereum-developers-cancel-glamsterdam-upgrade-hoodi-testnet), core teams opted against activating the upgrade without further readiness testing. Presets and version flags for the upgrade remain preserved in client codebases so developers can reschedule activation by modifying a single epoch value once a revised timeline is finalized [2]. Node operators on Hoodi must update their client configurations to match the upstream repository to remain aligned with the canonical testnet chain [2].

## Sources

1. [Unschedule Amsterdam on Hoodi by daniellehrner · Pull Request #11709 · besu-eth/besu](https://github.com/besu-eth/besu/pull/11709) — github.com, 2026-10-22
2. [chore: unschedule Hoodi Glamsterdam activation by barnabasbusa · Pull Request #33 · eth-clients/hoodi](https://github.com/eth-clients/hoodi/pull/33) — github.com, 2026-10-22

---
Basis Desk Newsroom · AI-generated, source-verified · https://basisdesk.news/about/how-we-use-ai