Skip to content

feat(deps): update erigon dependencies - #673

Merged
cjorge-graphops merged 2 commits into
mainfrom
renovate/erigon
Sep 5, 2026
Merged

cjorge-graphops merged 2 commits into
mainfrom
renovate/erigon

Conversation

@graphops-renovate

@graphops-renovate graphops-renovate Bot commented Aug 12, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
erigontech/erigon (source) minor v3.5.4 → v3.6.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

erigontech/erigon (erigontech/erigon)

v3.6.0

Compare Source

Erigon 3.6.0 is headlined by more reliable Caplin block production, pruned nodes reclaiming old snapshots, and
plain commitment snapshots, with leaner state access and maintenance throughout. Most 3.5 users can upgrade without
re-syncing. To benefit immediately from the new plain commitment format, existing users should install 3.6, then run
erigon seg reset --datadir=<path> before starting the node; the next start will re-sync using the new snapshots. Datadirs
created with Erigon 3.3 or earlier that have not already been rebased must use this reset path or run
erigon seg step-rebase --datadir=<path> --new-step-size=390625 before their first normal 3.6 start.

Highlights
  • More reliable Caplin block production. Caplin starts payload building before proposer slots and publishes fork
    choice earlier, giving blocks more time to reach attesters (#​23437, #​23172) — by @​lystopad
  • Pruned nodes now reclaim old state snapshots. State history, indexes, optional commitment history, and the receipts
    cache are retired once they fall outside their configured windows; fresh syncs also skip optional snapshots outside
    those windows. This fixes unbounded snapshot growth on long-running minimal and other pruned nodes (#​21306, #​22123,
    #​21200, #​22243, #​22349) — by @​AskAlexSharov, @​JkLondon
  • Plain commitment snapshots. New commitment files store values directly by default, speeding state reads and merges
    at the cost of larger files. Existing referenced files remain readable and convert lazily during merges; the offline
    integration commitment convert command provides an explicit migration path (#​14809, #​21452, #​21376, #​21933) — by
    @​awskii, @​AskAlexSharov
  • Faster state access and snapshot maintenance. Sharded LRU state, code, and commitment caches replace whole-cache
    resets; compression during state-snapshot merges is 2–3× faster, dictionary-building merges are about 1.5× faster,
    and the mainnet .bt pivot cache uses roughly one quarter of its previous heap (#​21386, #​21982, #​22154, #​21625,
    #​22050, #​21875) — by @​mh0lt, @​yperbasis, @​sudeepdino008, @​AskAlexSharov
Breaking Changes
  • Downgrading after 3.6 writes new snapshot files is unsupported. New 3.6 snapshot and accessor formats are
    incompatible with Erigon 3.5. Back up the datadir before upgrading if rollback is required (#​21452, #​21376, #​21778).
  • Historical receipts are off by default on fresh datadirs in every prune mode. Existing datadirs keep their stored
    enable/disable setting. Without the cache, receipt and log RPCs re-execute within the state-history window at higher
    latency. Blocks-mode operators who need receipts and logs back to genesis must use
    --prune.include-receipts --prune.receipts.distance=keep-all (#​22296, #​22349) — by @​yperbasis, @​AskAlexSharov
  • Idle polling filters expire after five minutes. Clients using eth_newFilter, eth_newBlockFilter, or
    eth_newPendingTransactionFilter must poll within the timeout or recreate the filter. Configure
    --rpc.subscription.filters.timeout, or set it to 0 to disable eviction. New subscriptions_active and
    subscriptions_*_total metrics track the filter lifecycle (#​22261) — by @​onelapahead
  • JSON-RPC compatibility changes. Quoted decimal block numbers such as "3" are rejected; use "0x3", a bare
    integer, or a named tag. Streaming trace errors no longer include result: null alongside error (#​21985, #​21922) —
    by @​lupin012
Added and Changed
RPC
  • With --prune.include-commitment-history, eth_getWitness now builds and verifies a lean witness for any block within
    retained history (#​22099) — by @​awskii
  • eth_fillTransaction fills missing fields and returns the unsigned raw transaction plus its JSON form, compatible
    with geth; KZG generation from raw blobs is not included (#​21870) — by @​lupin012
  • eth_getBalance, eth_getCode, eth_getStorageAt, eth_getTransactionCount, eth_getProof, and
    eth_getStorageValues now default an omitted block parameter to latest (#​21586) — by @​MysticRyuujin
  • trace_block and trace_replayBlockTransactions can include beacon-withdrawal balance changes through the optional
    IncludeWithdrawals trace setting (#​21592) — by @​lupin012
Consensus layer and protocol
Operations

Full Changelog: erigontech/erigon@v3.5.5...v3.6.0


v3.5.5

Compare Source

Erigon 3.6.0 is headlined by more reliable Caplin block production, pruned nodes reclaiming old snapshots, and
plain commitment snapshots, with leaner state access and maintenance throughout. Most 3.5 users can upgrade without
re-syncing. To benefit immediately from the new plain commitment format, existing users should install 3.6, then run
erigon seg reset --datadir=<path> before starting the node; the next start will re-sync using the new snapshots. Datadirs
created with Erigon 3.3 or earlier that have not already been rebased must use this reset path or run
erigon seg step-rebase --datadir=<path> --new-step-size=390625 before their first normal 3.6 start.

Highlights
  • More reliable Caplin block production. Caplin starts payload building before proposer slots and publishes fork
    choice earlier, giving blocks more time to reach attesters (#​23437, #​23172) — by @​lystopad
  • Pruned nodes now reclaim old state snapshots. State history, indexes, optional commitment history, and the receipts
    cache are retired once they fall outside their configured windows; fresh syncs also skip optional snapshots outside
    those windows. This fixes unbounded snapshot growth on long-running minimal and other pruned nodes (#​21306, #​22123,
    #​21200, #​22243, #​22349) — by @​AskAlexSharov, @​JkLondon
  • Plain commitment snapshots. New commitment files store values directly by default, speeding state reads and merges
    at the cost of larger files. Existing referenced files remain readable and convert lazily during merges; the offline
    integration commitment convert command provides an explicit migration path (#​14809, #​21452, #​21376, #​21933) — by
    @​awskii, @​AskAlexSharov
  • Faster state access and snapshot maintenance. Sharded LRU state, code, and commitment caches replace whole-cache
    resets; compression during state-snapshot merges is 2–3× faster, dictionary-building merges are about 1.5× faster,
    and the mainnet .bt pivot cache uses roughly one quarter of its previous heap (#​21386, #​21982, #​22154, #​21625,
    #​22050, #​21875) — by @​mh0lt, @​yperbasis, @​sudeepdino008, @​AskAlexSharov
Breaking Changes
  • Downgrading after 3.6 writes new snapshot files is unsupported. New 3.6 snapshot and accessor formats are
    incompatible with Erigon 3.5. Back up the datadir before upgrading if rollback is required (#​21452, #​21376, #​21778).
  • Historical receipts are off by default on fresh datadirs in every prune mode. Existing datadirs keep their stored
    enable/disable setting. Without the cache, receipt and log RPCs re-execute within the state-history window at higher
    latency. Blocks-mode operators who need receipts and logs back to genesis must use
    --prune.include-receipts --prune.receipts.distance=keep-all (#​22296, #​22349) — by @​yperbasis, @​AskAlexSharov
  • Idle polling filters expire after five minutes. Clients using eth_newFilter, eth_newBlockFilter, or
    eth_newPendingTransactionFilter must poll within the timeout or recreate the filter. Configure
    --rpc.subscription.filters.timeout, or set it to 0 to disable eviction. New subscriptions_active and
    subscriptions_*_total metrics track the filter lifecycle (#​22261) — by @​onelapahead
  • JSON-RPC compatibility changes. Quoted decimal block numbers such as "3" are rejected; use "0x3", a bare
    integer, or a named tag. Streaming trace errors no longer include result: null alongside error (#​21985, #​21922) —
    by @​lupin012
Added and Changed
RPC
  • With --prune.include-commitment-history, eth_getWitness now builds and verifies a lean witness for any block within
    retained history (#​22099) — by @​awskii
  • eth_fillTransaction fills missing fields and returns the unsigned raw transaction plus its JSON form, compatible
    with geth; KZG generation from raw blobs is not included (#​21870) — by @​lupin012
  • eth_getBalance, eth_getCode, eth_getStorageAt, eth_getTransactionCount, eth_getProof, and
    eth_getStorageValues now default an omitted block parameter to latest (#​21586) — by @​MysticRyuujin
  • trace_block and trace_replayBlockTransactions can include beacon-withdrawal balance changes through the optional
    IncludeWithdrawals trace setting (#​21592) — by @​lupin012
Consensus layer and protocol
Operations

Full Changelog: erigontech/erigon@v3.5.5...v3.6.0



Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

| datasource | package           | from   | to     |
| ---------- | ----------------- | ------ | ------ |
| docker     | erigontech/erigon | v3.5.4 | v3.6.0 |
@cjorge-graphops
cjorge-graphops merged commit 93de08d into main Sep 5, 2026
2 checks passed
@cjorge-graphops
cjorge-graphops deleted the renovate/erigon branch September 5, 2026 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant