Geth

Geth’s core team pushed out v1.17.7, a patch release triggered by a failed Ubuntu PPA publish of v1.17.6. The build adds a new flag for custom history pruning and folds in fixes touching the miner’s gas accounting and a memory leak in the chain’s block prefetcher.

• v1.17.7 was cut mainly because publishing v1.17.6 to the Ubuntu PPA failed
• Both v1.17.6 and v1.17.7 are certified ready for Sepolia’s Amsterdam fork on Oct 6, 2026
• A new –history.chain flag lets operators set a custom block-and-hash pruning point

• v1.17.7 latest Geth release tag, up from v1.17.6
• Oct 6 Sepolia’s Amsterdam fork activation date
• 5 new NodeOps bootnodes added to the client

The release is explicit about why it exists: “This is a quick release, cut mainly because publishing v1.17.6 to the Ubuntu PPA failed.” The notes add that “Both v1.17.6 and v1.17.7 are ready for the Amsterdam fork on Sepolia (Oct 6, 2026), so Sepolia validators can run either version,” meaning testnet validators are not forced onto the newer tag.

Custom History Pruning Lands via PR #35792

Node operators can now pick their own pruning point with –history.chain <block number>:<block hash>, shipped in pull request #35792. It works both for pruning an existing node through geth prune-history and for snap sync, where it skips downloading chain history before the chosen block.

That gives operators finer control over disk footprint than Geth’s prior fixed pruning presets.

Miner Gas Accounting Updated for EIP-8037

PR #35773 changes how the miner selects transactions for a block, now accounting for both execution and state gas under EIP-8037. This affects block builders and any operator running Geth as a miner or block-building client.

The release notes do not say which networks besides Sepolia have activated or scheduled EIP-8037, nor do they give a mainnet timeline.

Memory Leak Fix and Six Other Patches

PR #35821 fixes a memory leak by making the client wait for the block prefetcher to stop when the chain halts. Other changes in the same build: releasing pathdb clean caches when the database is disabled, encoding and hashing block-level access lists in one pipeline, restricting access-list fetches to blocks near the chain head, and restoring a txpool fallback that regressed in v1.17.3.

Five new multi-cloud bootnodes operated by NodeOps were also added alongside the existing bootnode set.

What Changes for Operators and Builders

Sepolia validators do not need to upgrade specifically for v1.17.7 since v1.17.6 already carries Amsterdam fork support; the update mainly fixes a packaging failure, not a consensus bug. Operators running low-storage or archive-adjacent nodes gain a new lever with –history.chain that was not available in v1.17.6 or earlier tags.

Miners and block-builder operators inherit the EIP-8037 gas-accounting change automatically on upgrade, since it alters transaction selection logic rather than adding an opt-in flag. The memory-leak fix in the prefetcher is a stability patch rather than a protocol change, relevant mainly to long-running nodes that previously saw creeping memory use on chain stalls.

This is a quick release, cut mainly because publishing v1.17.6 to the Ubuntu PPA failed.

Geth v1.17.7 release notes

The CCS read. A release forced by a packaging failure still shipped a real protocol-facing change in EIP-8037 gas accounting, a reminder that Geth’s patch cadence increasingly doubles as pre-fork plumbing for Sepolia rather than pure maintenance.

Sepolia’s Amsterdam fork activates Oct 6, 2026; validators on either v1.17.6 or v1.17.7 must be synced before that block.