# Ethereum postpones Hoodi's October 26 Glamsterdam test

Canonical: https://forkbrief.com/news/1e93ee4e-747b-4693-be07-6de1c7931882
Published: 2026-10-22T18:51:25.719Z
Publisher: Fork Brief

The planned testnet fork and gas-limit increase have been removed from configuration. Besu and Lodestar have published releases incorporating the postponement.

Ethereum has postponed Glamsterdam's October 26 activation on the Hoodi testnet. The [Ethereum Foundation's October 22 notice](https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay) withdraws the planned 17:42:48 UTC activation at epoch 132,352, with no replacement date. Developers want more time to investigate EIP-8037's interactions with mainnet smart contracts.

The change removes Amsterdam's execution-layer activation, Gloas's consensus-layer activation and the scheduled increase to a 200 million gas limit. It changes a future network configuration, without reverting Hoodi's existing chain history.

[Besu 26.10.1](https://github.com/besu-eth/besu/releases/tag/26.10.1), published October 22, describes itself as identical to 26.10.0 apart from the postponed Hoodi activation. The accompanying code change removes `amsterdamTime` from Hoodi's configuration. Nodes still running 26.10.0 retain the old activation until they run a release incorporating that change. Merging the change does not update those running nodes. The Besu release publishes two versioned build artifacts: a ZIP archive and a compressed TAR archive, each with a different SHA-256 checksum.

[Lodestar v1.50.1](https://github.com/ChainSafe/lodestar/releases/tag/v1.50.1), also released October 22, removes the Gloas fork and 200 million gas schedule. Its notes warn that v1.50.0 still contains the old Gloas activation. Hoodi operators are told to keep their existing pre-Gloas builder and relay settings until the fork is rescheduled, while also using an execution client with the activation removed. Consensus updates cover both the beacon node and validator client when running a validator.

Earlier [Prysm changes for Sepolia](https://forkbrief.com/news/a8310819-89ce-45a4-807f-32e2ebaa0473) concerned a separate rehearsal.

The [ACDE agenda](https://github.com/ethereum/pm/issues/2267) listed December 1, 8 and 9 as mainnet candidates, contingent on Hoodi proceeding smoothly. Those discussion options are not an adopted mainnet activation date.

## Sources

- [Lodestar v1.50.1: Hoodi Gloas unscheduled](https://github.com/ChainSafe/lodestar/releases/tag/v1.50.1) — ChainSafe Lodestar client team
- [All Core Devs Execution \#248, October 22, 2026 agenda](https://github.com/ethereum/pm/issues/2267) — Ethereum core-developer coordination
- [Glamsterdam on Hoodi Postponed](https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay) — Ethereum Foundation Protocol Cluster
- [Besu 26.10.1: Hoodi activation postponed](https://github.com/besu-eth/besu/releases/tag/26.10.1) — Besu client team
- [chore: unschedule Hoodi Glamsterdam activation](https://github.com/eth-clients/hoodi/pull/33) — Ethereum eth-clients Hoodi maintainers
- [Ethereum Scraps Glamsterdam’s Hoodi Fork After ChainSecurity Flags Gas Risks](https://unchainedcrypto.com/ethereum-scraps-glamsterdams-hoodi-fork-after-chainsecurity-flags-gas-risks/) — Unchained

- [Editorial policy](https://forkbrief.com/editorial-policy)
- [Request a correction](https://forkbrief.com/corrections)