You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key.
Patches
The issue is resolved in the v1.16.9 and v1.17.0 releases of Geth. We recommend rotating the node key after applying the upgrade, which can be done by removing the file <datadir>/geth/nodekey before starting Geth.
Credit
The issue was reported as a public pull request to go-ethereum by @fengjian.
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-26313, 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.
Highlights
Path-based Archive Node with Proofs
The path-based archive node can now serve proofs (via eth_getProof) for the state of older blocks.
You can configure the block range that supports proving independently from other archive state availability. Specifically, you can use the --history.trienode command-line flag to set the amount of blocks for which tree nodes will be tracked.
This feature is disabled by default. Note that state history cannot easily be recovered once deleted, as it can only be generated by processing blocks. However, you can enable trienode history (and/or state history) at any time to turn a full node into a partial archive node, keeping state from that point in time onwards.
OpenTelemetry tracing is now supported by the RPC server, including support for distributed tracing.
We have also added some tracing spans for block processing via the engine API, i.e. engine_newPayload.
The geth version-check subcommand has been removed. This command checked the geth website for signed vulnerability notices, and would tell if updates are necessary (#33498)
There is now a --miner.maxblobs command-line flag to set a limit on blobs included in built blocks (#33129, #33302)
Geth now supports continuous profiling with Grafana Pyroscope (#33623)
A rare bug that could halt block production in geth --dev mode was fixed (#33146)
A new --rpc.rangelimit flag configures the maximum block range for eth_getLogs (#33163)
geth --exitwhensynced will now set the finalized and safe block (#33038)
geth --ethstats now reports the newPayload processing time to the stats server (#33395)
Some work towards the migration of state to a binary tree has landed, and this replaces the Verkle Tree implementation (#33807, #33739, #33694, #32445, #33461)
Some access list semantics have been fixed while working on EIP-7928 Block-Level Access Lists (#33281, #33637, #33450)
Core
The crypto/ecies library allowed extraction of the private key used for key derivation via observation of response timing. We recommend rotating the node key after applying this update. (#33669)
When a missing block is encountered during tx unindexing, Geth will now skip it and move on instead of entering an infinite loop. (#33573)
Geth now optionally collect and export metrics about the total state size (#33254, #33376, #33415)
There is a new OnStateUpdate hook, which is called after all state of a block has been committed. This gives access to the changeset of the block. (#33490)
Pebble configuration has been tweaked for improved performance (#33697, #33353, #33315)
A rare crash in the log indexer related to reorg handling has been fixed (#33810)
Internal state diff size accounting has been corrected, so state diffs will now be flushed to the disk store less often (#33505)
Since the keccak256 hash function variant used by Ethereum no longer has a fast-path in the standard library, we have vendored the keccak implementation back into our repository (#33323)
Library
The RLP library now has a RawList type for dealing with un-decoded lists in a more convenient way (#33755, #33834, #33840, #33841)
The low-level RLP iterator and uses of it have been improved (#33245, #33188, #33820)
Clef can now sign blob transactions with cell proofs (#32910)
Fixed some corner-case bugs in metrics exporting (#33749, #33748)
The hardware wallet library now supports the Ledger Nano Gen5 and correctly enables EIP-712 signing for all supported versions. (#33297, #33113)
SignTextWithPassphrase now works correctly with all supported hardware wallets (#33138)
Some minor bugs were fixed in the keystore implementation (#33606, #33602, #33090)
The bitutil.XORBytes function has been deprecated in favor of stdlib package crypto/subtle (#33331)
A memory leak in the beacon chain light client was fixed (#33483)
RPC
eth_getTransactionByHash now returns the blockTimestamp as part of the transaction object (#33709)
Error codes for some conditions in eth_simulateV1, eth_getLogs, eth_getStorageAt have been improved to better comply with the execution RPC spec (#33007, #33320, #33282)
eth_simulateV1 now selects the correct set of precompiles for the simulated header (#33363)
eth_sendTransaction and eth_fillTransaction now default to EIP-1559 (#33058)
The GraphQL implementation has received some bug fixes for cases where a resolved item is not found. (#33184, #33225)
In GraphQL, the gasPrice is now retrievable for transaction types 0x3 and 0x4 (#33542)
The RPC server now enables plain-text HTTP2 for improved performance (#33812)
The RPC client no longer sends spurious RST_STREAM HTTP2 frames (#33122)
Some minor JSON encoding bugs have been fixed in ethclient (#33693, #33242, #33464)
The gethclient has a new wrapper of the callTracer (#31510)
In the callTracer, reported logs now contain an index field which is the index of the log within the transaction (#33629)
P2P Networking
The transaction pool heartbeat mechanism had some fixes for potential resource leaks (#33704)
The eth and snap protocol implementations nows validates most p2p messages before decoding their content. This improves security and sync performance in some cases. (#33835)
The blob transaction pool has seen some bug fixes and now accepts nonce-gapped transactions to a very limited extent (#32717, #33775, #33474, #33352, #33301, #33260)
Snap sync status is now tracked better, ensuring a snap sync will not be triggered accidentally by the engine API (#33157)
The snap sync scheduler was improved to better protect the trie database against accidential mutations while the node is processing blocks. This resolves some edge cases where the database could be corrupted (#33428)
The header sync implementation was fixed to better deal with setHead operations during sync (#33481)
Peer connections delivering stale transactions will be penalized less, since delivery of a few stale transactions is a common occurrence. (#32725)
Peers announcing transactions of one type, and delivering a different type, are now disconnected as penalty (#33378)
Similarly, peers delivering invalid KZG proofs will now be disconnected (5b99d2b)
The transaction pool has new metrics for the number of accounts with transactions (#33646, #33654)
For a full rundown of the changes please consult the Geth 1.17.0 release milestone.
As with all our previous releases, you can find the:
Pre-built binaries for all platforms on our downloads page.
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:
Pre-built binaries for all platforms on our downloads page.
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.
Add eth_sendRawTransactionSync which waits until either a timeout or the transaction is mined. This feature is mostly useful on L2s with lower blocktimes. (#32830, #32930, #32929)
Add support for eth_simulateV1 in ethclient (#32856)
Fix for an issue that might crash debug_traceCall (#33015)
Fix for an issuer where local transactions were not persisted to the journal (#32921)
Add geth --genesis flag as an alternative to running geth init genesis.json (#32844)
Fix for receipt insertion during ERA file import. (#32934)
Work on getting the trie node history in order to serve historical eth_getProof request with the new path-based archive node. (#32907, #32914, #32937)
Further work on cmd/keeper, our guest program for zkVMs (#32816)
⚠️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.
Add eth_sendRawTransactionSync which waits until either a timeout or the transaction is mined. This feature is mostly useful on L2s with lower blocktimes. (#32830, #32930, #32929)
Add support for eth_simulateV1 in ethclient (#32856)
Fix for an issue that might crash debug_traceCall (#33015)
Fix for an issuer where local transactions were not persisted to the journal (#32921)
Core
Add geth --genesis flag as an alternative to running geth init genesis.json (#32844)
Fix for receipt insertion during ERA file import. (#32934)
Work on getting the trie node history in order to serve historical eth_getProof request with the new path-based archive node. (#32907, #32914, #32937)
Further work on cmd/keeper, our guest program for zkVMs (#32816)
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.17.x release cycle, please update RPC client libraries to support cell-level (v1) proofs. (#32849)
eth_subscribe now supports a transactionReceipts subscription. There is also a wrapper in ethclient for this new subscription type. (#32697, #32869)
eth_simulateV1 was fixed to return the block timestamp in logs, like eth_getLogs does. (#32831)
In the abigen v2 runtime, BoundContract.Transfer will now verify that the contract has a payable fallback or receive method. (#32374)
A keccak256preimage tracer has been added. (#32569)
Networking
The eth protocol handler will now drop peers sending duplicated transactions. This is to unify behavior with other client implementations. (#32728)
A regression in the discovery system could cause high CPU usage under synthetic conditions (i.e. in tests). (#32912)
A very rare shutdown hang related to peer discovery is resolved. (#32572)
The eth protocol test suite has a new post-merge test chain and saw some bug fixes for flakey tests. (#32834, #32850)
Core
Our freezer implementation now supports partial reads, i.e. reading just a slice out of a larger stored value. This functionality is used for the archive node state history. (#32132)
The trie database now implements a storage layer for 'trie history', a precursor to serving historical state proofs for the path-based archive node. (#32596)
The txpool/valid.meter metric has been corrected. (#32845)
The engine API saw some fixes related to fork compatibility checks. (#32800, #32731)
For a full rundown of the changes please consult the Geth 1.16.5 release milestone.
As with all our previous releases, you can find the:
Pre-built binaries for all platforms on our downloads page.
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.16.8 [security]
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Feb 19, 2026
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security] - abandoned
Mar 24, 2026
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security] - abandoned
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Mar 24, 2026
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security] - abandoned
Mar 27, 2026
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security] - abandoned
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Mar 30, 2026
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
Apr 9, 2026
renovateBot
changed the title
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Apr 9, 2026
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
Apr 9, 2026
renovateBot
changed the title
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Apr 14, 2026
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
Apr 14, 2026
renovateBot
changed the title
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Apr 15, 2026
renovateBot
changed the title
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
Apr 15, 2026
renovateBot
changed the title
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.0 [security]
Apr 15, 2026
renovateBot
changed the title
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY] - autoclosed
Jun 4, 2026
renovateBot
deleted the
renovate/go-github.com-ethereum-go-ethereum-vulnerability
branch
June 4, 2026 09:43
renovateBot
changed the title
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY] - autoclosed
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
Jun 4, 2026
renovateBot
changed the title
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY] - autoclosed
Jun 21, 2026
renovateBot
changed the title
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY] - autoclosed
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]
Jun 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.16.4→v1.17.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
go-ethereum is vulnerable to DoS via malicious p2p message affecting a vulnerable node
CVE-2026-22862 / GHSA-mr7q-c9w9-wh4h
More information
Details
Impact
A vulnerable node can be forced to shutdown/crash using a specially crafted message.
More details to be released later.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by DELENE TCHIO ROMUALD.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
go-ethereum is vulnerable to high CPU usage leading to DoS via malicious p2p message
CVE-2026-22868 / GHSA-mq3p-rrmp-79jg
More information
Details
Impact
An attacker can cause high CPU usage by sending a specially crafted p2p message.
More details to be released later.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by @Yenya030
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Go Ethereum affected by DoS via malicious p2p message
CVE-2026-26313 / GHSA-689v-6xwf-5jf3
More information
Details
Impact
An attacker can cause high memory usage by sending a specially-crafted p2p message.
More details to be released later.
Patches
The issue is resolved in the v1.17.0 release.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by @revofusion
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Go Ethereum affected by DoS via malicious p2p message
CVE-2026-26314 / GHSA-2gjw-fg97-vg3r
More information
Details
Impact
A vulnerable node can be forced to shutdown/crash using a specially crafted message.
More details to be released later.
Patches
The problem is resolved in the v1.16.9 and v1.17.0 releases of Geth.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by Waleed Ahmed from vulsight.com
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake
CVE-2026-26315 / GHSA-m6j8-rg6r-7mv8
More information
Details
Impact
Through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key.
Patches
The issue is resolved in the v1.16.9 and v1.17.0 releases of Geth. We recommend rotating the node key after applying the upgrade, which can be done by removing the file
<datadir>/geth/nodekeybefore starting Geth.Credit
The issue was reported as a public pull request to go-ethereum by @fengjian.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
ethereum/go-ethereum (github.com/ethereum/go-ethereum)
v1.17.0: Eezo-Inlaid Circuitry (v1.17.0)Compare Source
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-26313, 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/nodekeyfile before restarting geth. Note this will cause a change in the p2p node ID, which may break static peering setups.Highlights
Path-based Archive Node with Proofs
The path-based archive node can now serve proofs (via
eth_getProof) for the state of older blocks.You can configure the block range that supports proving independently from other archive state availability. Specifically, you can use the
--history.trienodecommand-line flag to set the amount of blocks for which tree nodes will be tracked.This feature is disabled by default. Note that state history cannot easily be recovered once deleted, as it can only be generated by processing blocks. However, you can enable trienode history (and/or state history) at any time to turn a full node into a partial archive node, keeping state from that point in time onwards.
#32727, #32621, #33551, #32981, #33399, #32913, #33303, #33584, #33329, #33681, #33103, #33098, #33515, #32247
EraE History Support
Geth now suports the EraE file format, an archival format for post-merge chain history.
#32157, #33827
OpenTelemetry Tracing
OpenTelemetry tracing is now supported by the RPC server, including support for distributed tracing.
We have also added some tracing spans for block processing via the engine API, i.e.
engine_newPayload.#33599, #33452, #33780, #33521
All Changes
Geth CLI
geth version-checksubcommand has been removed. This command checked the geth website for signed vulnerability notices, and would tell if updates are necessary (#33498)--miner.maxblobscommand-line flag to set a limit on blobs included in built blocks (#33129, #33302)geth --devmode was fixed (#33146)--rpc.rangelimitflag configures the maximum block range foreth_getLogs(#33163)geth --exitwhensyncedwill now set thefinalizedandsafeblock (#33038)geth --ethstatsnow reports the newPayload processing time to the stats server (#33395)evm blocktestcommand can now read filenames from stdin when no path is provided (#32824)Fork Implementation
Core
OnStateUpdatehook, which is called after all state of a block has been committed. This gives access to the changeset of the block. (#33490)setHeadoperation now unsets the finalized block, in cases where the rolled-back block range extends before it. (#33486)SignatureValuesmethod oftypes.Signernow reports an error for invalid signature sizes (#33647)Library
SignTextWithPassphrasenow works correctly with all supported hardware wallets (#33138)bitutil.XORBytesfunction has been deprecated in favor of stdlib package crypto/subtle (#33331)RPC
eth_getTransactionByHashnow returns theblockTimestampas part of the transaction object (#33709)eth_simulateV1,eth_getLogs,eth_getStorageAthave been improved to better comply with the execution RPC spec (#33007, #33320, #33282)eth_simulateV1now selects the correct set of precompiles for the simulated header (#33363)eth_sendTransactionandeth_fillTransactionnow default to EIP-1559 (#33058)gasPriceis now retrievable for transaction types 0x3 and 0x4 (#33542)ethclient(#33693, #33242, #33464)gethclienthas a new wrapper of thecallTracer(#31510)callTracer, reported logs now contain anindexfield which is the index of the log within the transaction (#33629)P2P Networking
setHeadoperations during sync (#33481)5b99d2b)For a full rundown of the changes please consult the Geth 1.17.0 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.16.9: Shield Focusing Module (v1.16.9)Compare Source
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/nodekeyfile 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:
ethereum/client-go(use "stable" tag).v1.16.8: Moisture Filters (v1.16.8)Compare Source
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:
ethereum/client-go(use "stable" tag).v1.16.7: Ballistic Drift Stabilizer (v1.16.7)Compare Source
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 available blob capacity.
2025-12-092026-01-07Fusaka
geth --devmode (#32917)RPC
eth_sendRawTransactionSyncwhich waits until either a timeout or the transaction is mined. This feature is mostly useful on L2s with lower blocktimes. (#32830, #32930, #32929)eth_simulateV1in ethclient (#32856)debug_traceCall(#33015)Core
geth --genesisflag as an alternative to runninggeth init genesis.json(#32844)eth_getProofrequest with the new path-based archive node. (#32907, #32914, #32937)Networking
For a full rundown of the changes please consult the Geth 1.16.6 and 1.16.7 release milestones.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.16.6: Leather Wrapping (v1.16.6)Compare Source
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-09and2026-01-07respectively.Fusaka
geth --devmode (#32917)RPC
eth_sendRawTransactionSyncwhich waits until either a timeout or the transaction is mined. This feature is mostly useful on L2s with lower blocktimes. (#32830, #32930, #32929)eth_simulateV1in ethclient (#32856)debug_traceCall(#33015)Core
geth --genesisflag as an alternative to runninggeth init genesis.json(#32844)eth_getProofrequest with the new path-based archive node. (#32907, #32914, #32937)Networking
For a full rundown of the changes please consult the Geth 1.16.6 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go.v1.16.5: Coolant Cells (v1.16.5)Compare Source
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_sendRawTransactionhas 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.17.x release cycle, please update RPC client libraries to support cell-level (v1) proofs. (#32849)eth_subscribenow supports atransactionReceiptssubscription. There is also a wrapper in ethclient for this new subscription type. (#32697, #32869)eth_simulateV1was fixed to return the block timestamp in logs, likeeth_getLogsdoes. (#32831)BoundContract.Transferwill now verify that the contract has a payable fallback or receive method. (#32374)keccak256preimagetracer has been added. (#32569)Networking
Core
txpool/valid.metermetric has been corrected. (#32845)For a full rundown of the changes please consult the Geth 1.16.5 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.