This is a quick release, cut mainly because publishing v1.17.6 to the Ubuntu PPA failed. It also carries a few fixes merged since then. 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. Users can now also choose their own history pruning point with --history.chain <block number>:<block hash>. It works both for pruning…
This is a maintenance release with a number of performance improvements to block processing and initial sync, and is recommended for all users. A few things worth highlighting: The Amsterdam hardfork is scheduled on the Sepolia testnet at timestamp 1791294816 (Oct 6, 2026, 13:53:36 UTC). Sepolia node operators must upgrade before that time. The Holesky testnet has been removed, as the network reac…
This is a maintenance release with accumulated bug fixes and improvements, and is recommended for all users. It continues the implementation work for the upcoming Amsterdam hardfork. A few things worth highlighting: The default GOGC has changed from 20 to 50, trading a higher memory peak for less GC overhead. Set --gogc=20 to keep the old behavior. Pebble v2 is now supported as a key-value store b…
This is a maintenance release with accumulated bug fixes and improvements, and is recommended for all users. It also continues the implementation work for the upcoming Amsterdam hardfork. One thing worth highlighting: Clef has been removed. The standalone clef signer has moved to https://github.com/ethereum/clef (#35097). Fork Implementation (Amsterdam) EIP-7928: Block-Level Access Lists: the bloc…
This is a maintenance release with continued progress on the Amsterdam fork implementation. It also introduces ETH/70, which is now live on the network. Breaking change for tracing APIs (debug_trace*), specifically the structLog (opcode) tracer. The following response fields now follow the newly established client-wide spec (ethereum/execution-apis#762) and reexec has been removed from the tracing…
This is a maintenance release with several important bug fixes. Notably, a critical issue in debug_executionWitness could previously corrupt node data, users relying on this RPC endpoint are strongly advised to upgrade. Geth now also supports syncing with chains where pre-Prague history has been pruned, and allows explicitly removing it via geth prune-history --history.chain postprague. Geth Set d…
This is a bug fix release and is recommended for all users. It resolves a regression in snap sync, as well as several security issues. Geth The engine API no longer enables plain-text HTTP2, due to some reports of incompatibilities with the teku CL (#33922) The new --metrics.influxdb.interval flag allows changing the metrics reporting interval. (#33767) Geth has a new inspect-trie subcommand that…
This is a feature release, with all accumulated development from the last 3 months. See below for the highlights. Note that this release contains multiple critical security fixes, as well as many bug fixes, and is recommended for all users. However, if you are cautious about upgrades, you can also install v1.16.9 which has just the critical security fixes. Specifically, this release fixes CVE-2026…
This is a security hot-fix release. Specifically, this release fixes CVE-2026-26314, CVE-2026-26315. We recommend recreating your p2p node key after installing this update, which you can do by removing the DATADIR/geth/nodekey file before restarting geth. Note this will cause a change in the p2p node ID, which may break static peering setups. As with all our previous releases, you can find the: Pr…
This is a security fix release and is recommended for all users. It resolves two p2p vulnerabilities reported through the Ethereum Foundation bug bounty program. As with all our previous releases, you can find the: Pre-built binaries for all platforms on our downloads page. Docker images published under ethereum/client-go (use "stable" tag). Ubuntu packages in our Launchpad PPA repository. macOS p…
This is a re-roll of v1.16.6, including an important fix in the KZG cryptography library. This release enables the Fusaka hardfork on Ethereum mainnet. The Fusaka fork is scheduled to occur at 2025-12-03 21:49:11 UTC. Please upgrade your node to v1.16.7 in time for the fork. This release also enables two blob-parameter-only (BPO) upgrades. These upgrades change protocol parameters to increase the…
⚠️ Do not use v1.16.6 for the Fusaka upgrade! Please use v1.16.7, which contains an important security fix. ⚠️ This release enables the Fusaka hardfork on Ethereum mainnet The fork is scheduled to occur at 2025-12-03 21:49:11 UTC. This release also enables the BPO1 and BPO2 forks for mainnet at 2025-12-09 and 2026-01-07 respectively. Fusaka Set mainnet timestamps for Osaka (#33063) Enable Fusaka f…
This is a maintenance release. We are issuing this release mostly to add a conversion path for blob proofs submitted via eth_sendRawTransaction. See https://blog.ethereum.org/2025/10/15/fusaka-blob-update for more information. RPC eth_sendRawTransaction has an upgrade path for blob proofs after the Fusaka fork. Note this is temporary. We will remove support for blob proof conversion during the v1.…