The Go Ethereum team has released Geth v1.17.5, a maintenance update containing accumulated bug fixes, performance improvements and additional work for Ethereum’s next execution-layer upgrade. The project published the release on July 27, 2026, and recommended it for all Geth users.
Geth, one of Ethereum’s major execution clients, is responsible for processing transactions, maintaining network state and communicating with the consensus client used by a node. Version 1.17.5 is available through the project’s official download page and GitHub repository, where operators can review the full changelog and obtain platform-specific binaries.
Pebble v2 Arrives With a Controlled Migration Path
The release adds support for Pebble v2 as Geth’s key-value database backend. New nodes initialized from scratch will use the newer version automatically, while installations with an existing Pebble v1 database will continue operating on the earlier backend. Geth does not automatically migrate legacy databases to Pebble v2 during a routine software update.
Operators who want to convert an existing database must run the dedicated geth db pebble-upgrade command. The explicit migration path reduces the risk of an unexpected database-format change during startup, but it also means node administrators should assess storage, backup and operational requirements before initiating the conversion.
The update also changes Geth’s default Go garbage-collection setting from 20 to 50. According to the release notes, this configuration accepts a higher peak in memory consumption in exchange for reducing garbage-collection overhead. Operators who prefer the previous memory behavior can retain it by launching Geth with --gogc=20.
Beyond database and memory management, v1.17.5 introduces a sparse blob transaction pool intended to reduce memory usage, optimizes block validation and addresses several synchronization, networking and transaction-processing issues. The release is broader than a storage-backend update, combining operational fixes with incremental efficiency improvements across the client.
Amsterdam Implementation Continues Ahead of Glamsterdam
Geth v1.17.5 also advances implementation of several proposals being developed for Amsterdam, the execution-layer component of Ethereum’s broader Glamsterdam upgrade. The release includes work involving block-level access lists, state-creation and state-access gas costs, builder execution requests and increased maximum contract size. These additions represent ongoing client development rather than confirmation that every listed proposal has reached final mainnet status.
Ethereum uses the name Glamsterdam for the combined network upgrade, merging Amsterdam on the execution layer with Gloas on the consensus layer. Official Ethereum documentation currently places the upgrade in the second half of 2026 and says it is intended to improve Layer 1 scalability, block processing and long-term database sustainability. A final mainnet activation date was not listed in the official roadmap material reviewed.
The Ethereum Foundation has explained that client teams must first stabilize implementations through development networks, complete security reviews and move the upgrade through public testnets before confirming the mainnet fork date. The Amsterdam-related code in v1.17.5 is therefore part of the preparation process, not evidence that the network upgrade has already activated.
Node operators can install v1.17.5 as a standard maintenance release, but database migration should be treated as a separate administrative decision. The immediate operational priority is to review memory requirements, database compatibility and the official release notes before updating production infrastructure. Future Geth versions are expected to continue refining Amsterdam support as Ethereum’s testing process progresses.