fix(deps): update module github.com/ethereum/go-ethereum to v1.17.4 - autoclosed#370
Closed
renovate[bot] wants to merge 1 commit into
Closed
fix(deps): update module github.com/ethereum/go-ethereum to v1.17.4 - autoclosed#370renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/github.com-ethereum-go-ethereum-1.x
branch
from
June 22, 2026 10:51
5fa1712 to
ec78616
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.11.6→v1.17.4Release Notes
ethereum/go-ethereum (github.com/ethereum/go-ethereum)
v1.17.4: Flexible Polymer Casing (v1.17.4)Compare Source
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:
clefsigner has moved to https://github.com/ethereum/clef (#35097).Fork Implementation (Amsterdam)
OnGasChangeV2hook for multi-dimensional gas (#34946)engine_newPayloadWithWitnessV5has been added and the witness format now uses the canonical spec field ordering (#35009)evm t8ntooling has been updated for Amsterdam, adding BAL and slot-number support and binary-trie leaf export (#34843, #35025)Geth
--memory) when one is set (#34947)RPC
eth_baseFeehas been added, returning the base fee of the next block (#34904, #35023)eth_capabilitieshas been added, letting clients discover which historical data a node can serve (#33886)debug_clearTxpoolhas been added to clear the transaction pool (#33347, #35130)State-reading methods (
eth_getBalance,eth_getCode,eth_getStorageAt, etc.) now default the block parameter tolatestwhen omitted (#35100)Fixes for
eth_simulateV1: an incorrect "base fee too low" error code and a pre-Shanghai withdrawal regression (#34951, #34939)debug_setHeadnow propagates rewind errors instead of silently ignoring them (#35001)EIP-7702 transactions with a nil
Toaddress are now rejected (#35094)HTTP RPC responses now always set
Content-Length, and a WebSocket handshake status-code bug was fixed (#35072, #35111)The client can now configure trace-context propagation via the
traceparentheader, and response writes are now traced (#35132, #35049)GraphQL
begin > 0andend == 0are now rejected (#35032)Block.rawresolver now returns empty bytes when the block body is missing (#35027)Core
Engine API & Blobs
engine_hasBlobshas been added, andengine_getBlobsnow counts only actually-available blobs (#34859, #35028)GetBlobsrequests reduces engine API latency, and otel tracing has been added to the GetBlobs endpoints (#35124, #35026)testing_commitBlockV1has been added as the write companion totesting_buildBlockV1(#34995)Networking
For a full rundown of the changes please consult the Geth 1.17.4 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.17.3: Enzymatic Injector (v1.17.3)Compare Source
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
reexechas been removed from the tracing config:memory: words are 0x-prefixed and padded to 32 bytesstorage: keys and values are 0x-prefixederror: omitted when empty (previously serialized as "")Geth
Core
snap/2protocol (#34083, #34649, #34654, #34874)slotNumberand fix block value collection in pre-Amsterdam engine API payloads (#34704)Networking
Cryptography
RPC
reexecfrom tracing config (#34093)eth_estimateGas(#34081)eth_call(#34842)MaxUsedGastoeth_simulatecall results (#34820)eth_syncing(#34633)eth_getLogs,eth_getFilterLogs, …) when the block range limit is exceeded (#34647)Others
For a full rundown of the changes please consult the Geth 1.17.3 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.17.2: EMF Suppressor (v1.17.2)Compare Source
This is a maintenance release with several important bug fixes. Notably, a critical issue in
debug_executionWitnesscould 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
fetchpayloadcommand to build execution witnesses for specific blocks (#33919)womirtarget for keeper (#34079)geth snapshot traverse-stateandgeth snapshot traverse-rawstate(#34051)Core
VerifyCellProofBatch(#33963)Networking
RPC
debug_executionWitness; deprecateddebug_executionWitnessByHash(#33931)eth_simulateV1response (#32789)eth_simulateV1(#33952)eth_createAccessListto return an empty list instead of null for storage keys (#33976)eth_getFilterLogsnow returns an error if the requested chain segment has been pruned (#33823)eth_simulateV1(#34616)eth_getProof(#34617)Observability
Build
For a full rundown of the changes please consult the Geth 1.17.2 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.17.1: Eezo Shunt (v1.17.1)Compare Source
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
--metrics.influxdb.intervalflag allows changing the metrics reporting interval. (#33767)inspect-triesubcommand that prints information about node counts at all state trie depths (#28892)Core
Networking
RPC
eth_estimateGasnow honors the user-supplied access list (#33849)eth_getStorageValues(#32591)testing_buildBlockV1(#33656)Build
For a full rundown of the changes please consult the Geth 1.17.1 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).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
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.