---
title: "Geth Delays Amsterdam Hard Fork on Hoodi Testnet in v1.17.10 Release"
description: "Ethereum client developers postpone the scheduled Oct. 26 upgrade on the Hoodi test network, requiring node operators to patch."
url: https://basisdesk.news/news/geth-delays-amsterdam-hard-fork-hoodi-testnet
published: 2026-10-23T13:03:55.979Z
modified: 2026-10-23T13:03:55.979Z
section: Tech & Protocols
author: Basis Desk Newsroom (AI-generated, source-verified)
sentiment: neutral
tickers: [ETH]
tags: [geth, ethereum, hard-fork, testnet, hoodi]
license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice.
---

# Geth Delays Amsterdam Hard Fork on Hoodi Testnet in v1.17.10 Release

Ethereum client developers postpone the scheduled Oct. 26 upgrade on the Hoodi test network, requiring node operators to patch.

## At a glance

- **What happened:** Go-Ethereum released client version 1.17.10 on Oct. 23, postponing the Amsterdam fork on the Hoodi testnet previously scheduled for Oct. 26.
- **Why it matters:** The change prevents node divergence on Hoodi, while other Ethereum networks and forks remain unaffected.
- **Who is affected:** Hoodi testnet node operators running Geth v1.17.9.
- **Takes effect:** Oct. 26, 2026, 17:42:48 UTC
- **What's next:** Ethereum client developers will schedule a new Hoodi Amsterdam fork date in an upcoming release.
- **Status:** announced
- **Primary source:** [Soil Reducer (v1.17.10)](https://github.com/ethereum/go-ethereum/releases/tag/v1.17.10) — Geth releases

## Key points

- Geth v1.17.10 postpones the Amsterdam hard fork on the Hoodi testnet, previously set for Oct. 26, 2026, at 17:42:48 UTC.
- Hoodi node operators running client v1.17.9 must update before the original Oct. 26 timestamp, while other networks are unaffected.
- The release configures snap sync to switch to snap/2 automatically when Amsterdam goes live and optimizes EVM DUP/SWAP dispatch.

## Editorial remark

- **Context:** The Amsterdam upgrade is part of Ethereum's ongoing hard fork roadmap, tested on designated testnets like Hoodi before mainnet deployment.
- **Impact:** Hoodi testnet validators and infrastructure providers must upgrade Geth versions immediately to avoid network divergence.
- **Watch:** Release notes for the next Geth update confirming the rescheduled activation block and timestamp for the Hoodi Amsterdam fork.

Ethereum execution client Go-Ethereum (Geth) deployed version 1.17.10 on Oct. 23 to postpone the Amsterdam hard fork on the Hoodi testnet [1]. The upgrade had been targeted for activation on Oct. 26, 2026, at 17:42:48 UTC [1]. Node operators running Geth v1.17.9 on Hoodi must upgrade to the latest client release prior to that timestamp to stay synchronized [1].

The development team confirmed that other networks remain unaffected by the delay [1]. A revised activation date for the Amsterdam hard fork on Hoodi will be announced in a future software release [1]. At the time of writing, Ethereum's native asset, $ETH, was trading at $2,401.

## Client Optimizations and Sync Updates

Beyond calling off the testnet activation, Geth v1.17.10 introduces automated sync adjustments ahead of the Amsterdam hard fork [1]. The client will now automatically transition snap sync to the snap/2 protocol once the Amsterdam upgrade activates [1]. Node operators retain manual control over the feature through configuration flags `--snap.v2=true` or `--snap.v2=false` [1].

The patch also incorporates virtual machine execution enhancements, specifically optimizing DUP and SWAP dispatch within the EVM interpreter [1]. Software updates have been distributed across Geth's standard packaging channels, including Docker images under the stable tag, Ubuntu Launchpad PPAs, Homebrew taps, and pre-built binaries [1].

## Sources

1. [Soil Reducer (v1.17.10)](https://github.com/ethereum/go-ethereum/releases/tag/v1.17.10) — Geth releases, 2026-10-23

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