Skip to content

build(deps): bump the reth group across 1 directory with 9 updates#230

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/reth-214b661c82
Open

build(deps): bump the reth group across 1 directory with 9 updates#230
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/reth-214b661c82

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 10, 2026

Bumps the reth group with 7 updates in the / directory:

Package From To
reth-chainspec v1.10.2 v2.0.0
reth-errors v1.10.2 v2.0.0
reth-ethereum-forks v1.10.2 v2.0.0
reth-ethereum-primitives v1.10.2 v2.0.0
reth-evm v1.10.2 v2.0.0
reth-evm-ethereum v1.10.2 v2.0.0
reth-revm v1.10.2 v2.0.0

Updates reth-chainspec from v1.10.2 to v2.0.0

Release notes

Sourced from reth-chainspec's releases.

Reth v2.0.0

Dark (Banner)

Read our Blog Post

Reth 2.0 is a major release that makes Storage V2 the default for all new nodes, introduces the SparseTrieCacheTask for dramatically faster state root computation, and delivers across-the-board performance improvements to the engine, RPC, and P2P layers. This release also removes the deprecated reth-primitives crate and removes RocksDB feature gates (RocksDB is now always available).

Storage v2

Storage v2 is now the default for new nodes (#22890). Existing storage v1 nodes are unaffected and will continue to work.

For v2 snapshots, check out our renovated portal https://snapshots.reth.rs/.

We recommend downloading the snapshots with the --resumable flag, this will be enabled by default in the next release.

[!NOTE] Support for storage v1 nodes will be removed in a future version. An exact deprecation date will be communicated separately, all users are strongly encouraged to switch to storage v2.

[!IMPORTANT] If you rely on out-of-process database access concurrently with a running reth node (e.g. out of process block builders), with storage v2 holding a long read transaction might result in persistence stall if a reorg happens at the same time. In combination with engine backpressure this might cause the node to stall if the external reader holds the read transaction for too long.

Backwards Compatibility

  • If you start a new node with storage v2, you will not be able to use it with storage v1, and vice versa.
  • Reth 2.0 includes engine backpressure. This is a safeguard that prevents unbounded growth of in-memory blocks buffer in cases when persistence is not able to keep up with the chain. When the gap between canonical tip and the last persisted block exceeds --engine.persistence-backpressure-threshold (default: 16), no new payloads are executed until persistence advances. For SDK users, TreeConfig::with_persistence_backpressure_threshold provides the same functionality.
  • reth-primitives-traits crate was moved to a separate reth-core repo, along with other supporting crates. We kept the re-exports, so it should not affect the code that uses Reth as a library. If you depend on reth-primitives-traits directly, you need to switch to crates.io.
  • ExEx WAL encoding was changed from bincode to RLP for block serialization.

Dependencies

Compatible versions:

revm: 36.0.0 alloy-*: 1.8.2 alloy-evm: 0.30.0 revm-inspectors: 0.36.0

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Priority
Payload Builders High
Non-Payload Builders High

See Update Priorities for more information about this table.

Breaking Changes

SDK

... (truncated)

Changelog

Sourced from reth-chainspec's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

  • Create a new branch (e.g. release/vx.y.z) and open a pull request for it
  • Ensure all tests and lints pass for the chosen commit
  • Version bump
    • Update the version in all Cargo.toml's
  • Commit the changes
    • The message format should be release: vx.y.z, substituting x.y.z for the semver.
  • The PR should be reviewed to see if anything was missed
  • Once reviewed, merge the PR

Releasing

  • Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
  • Push the tag (git push origin vx.y.z)[^1]
  • Update Homebrew Tap
  • Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
    • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

  • A summary of the release (highlights etc.)
  • The update priority (see below)
  • An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits
  • eb4c15e chore: remove changelog workflow and .changelog directory (#23376)
  • 9320216 chore: 2.0 release branch (#23372)
  • 01d851c fix: unmount schelk volume before recover in snapshot script (#23371)
  • 2155fb7 chore: added block_access_list_raw rpc (#23363)
  • a539daf feat(trie): add DecodedMultiProofV2::from_witness constructor (#23362)
  • 6b176ab feat: expose EVM config on EthTransactionValidator (#23369)
  • 0e4f143 feat: catch-up for read-only ProviderFactorys (#23357)
  • 1a72883 chore(deps): weekly cargo update (#23359)
  • adc9601 refactor(rocksdb): use secondary instances for read only providers (#23346)
  • f3e813c fix(ci): fix Grafana URL year-2082 when ABBA disabled (#23348)
  • Additional commits viewable in compare view

Updates reth-errors from v1.10.2 to v2.0.0

Release notes

Sourced from reth-errors's releases.

Reth v2.0.0

Dark (Banner)

Read our Blog Post

Reth 2.0 is a major release that makes Storage V2 the default for all new nodes, introduces the SparseTrieCacheTask for dramatically faster state root computation, and delivers across-the-board performance improvements to the engine, RPC, and P2P layers. This release also removes the deprecated reth-primitives crate and removes RocksDB feature gates (RocksDB is now always available).

Storage v2

Storage v2 is now the default for new nodes (#22890). Existing storage v1 nodes are unaffected and will continue to work.

For v2 snapshots, check out our renovated portal https://snapshots.reth.rs/.

We recommend downloading the snapshots with the --resumable flag, this will be enabled by default in the next release.

[!NOTE] Support for storage v1 nodes will be removed in a future version. An exact deprecation date will be communicated separately, all users are strongly encouraged to switch to storage v2.

[!IMPORTANT] If you rely on out-of-process database access concurrently with a running reth node (e.g. out of process block builders), with storage v2 holding a long read transaction might result in persistence stall if a reorg happens at the same time. In combination with engine backpressure this might cause the node to stall if the external reader holds the read transaction for too long.

Backwards Compatibility

  • If you start a new node with storage v2, you will not be able to use it with storage v1, and vice versa.
  • Reth 2.0 includes engine backpressure. This is a safeguard that prevents unbounded growth of in-memory blocks buffer in cases when persistence is not able to keep up with the chain. When the gap between canonical tip and the last persisted block exceeds --engine.persistence-backpressure-threshold (default: 16), no new payloads are executed until persistence advances. For SDK users, TreeConfig::with_persistence_backpressure_threshold provides the same functionality.
  • reth-primitives-traits crate was moved to a separate reth-core repo, along with other supporting crates. We kept the re-exports, so it should not affect the code that uses Reth as a library. If you depend on reth-primitives-traits directly, you need to switch to crates.io.
  • ExEx WAL encoding was changed from bincode to RLP for block serialization.

Dependencies

Compatible versions:

revm: 36.0.0 alloy-*: 1.8.2 alloy-evm: 0.30.0 revm-inspectors: 0.36.0

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Priority
Payload Builders High
Non-Payload Builders High

See Update Priorities for more information about this table.

Breaking Changes

SDK

... (truncated)

Changelog

Sourced from reth-errors's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

  • Create a new branch (e.g. release/vx.y.z) and open a pull request for it
  • Ensure all tests and lints pass for the chosen commit
  • Version bump
    • Update the version in all Cargo.toml's
  • Commit the changes
    • The message format should be release: vx.y.z, substituting x.y.z for the semver.
  • The PR should be reviewed to see if anything was missed
  • Once reviewed, merge the PR

Releasing

  • Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
  • Push the tag (git push origin vx.y.z)[^1]
  • Update Homebrew Tap
  • Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
    • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

  • A summary of the release (highlights etc.)
  • The update priority (see below)
  • An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits
  • eb4c15e chore: remove changelog workflow and .changelog directory (#23376)
  • 9320216 chore: 2.0 release branch (#23372)
  • 01d851c fix: unmount schelk volume before recover in snapshot script (#23371)
  • 2155fb7 chore: added block_access_list_raw rpc (#23363)
  • a539daf feat(trie): add DecodedMultiProofV2::from_witness constructor (#23362)
  • 6b176ab feat: expose EVM config on EthTransactionValidator (#23369)
  • 0e4f143 feat: catch-up for read-only ProviderFactorys (#23357)
  • 1a72883 chore(deps): weekly cargo update (#23359)
  • adc9601 refactor(rocksdb): use secondary instances for read only providers (#23346)
  • f3e813c fix(ci): fix Grafana URL year-2082 when ABBA disabled (#23348)
  • Additional commits viewable in compare view

Updates reth-ethereum-forks from v1.10.2 to v2.0.0

Release notes

Sourced from reth-ethereum-forks's releases.

Reth v2.0.0

Dark (Banner)

Read our Blog Post

Reth 2.0 is a major release that makes Storage V2 the default for all new nodes, introduces the SparseTrieCacheTask for dramatically faster state root computation, and delivers across-the-board performance improvements to the engine, RPC, and P2P layers. This release also removes the deprecated reth-primitives crate and removes RocksDB feature gates (RocksDB is now always available).

Storage v2

Storage v2 is now the default for new nodes (#22890). Existing storage v1 nodes are unaffected and will continue to work.

For v2 snapshots, check out our renovated portal https://snapshots.reth.rs/.

We recommend downloading the snapshots with the --resumable flag, this will be enabled by default in the next release.

[!NOTE] Support for storage v1 nodes will be removed in a future version. An exact deprecation date will be communicated separately, all users are strongly encouraged to switch to storage v2.

[!IMPORTANT] If you rely on out-of-process database access concurrently with a running reth node (e.g. out of process block builders), with storage v2 holding a long read transaction might result in persistence stall if a reorg happens at the same time. In combination with engine backpressure this might cause the node to stall if the external reader holds the read transaction for too long.

Backwards Compatibility

  • If you start a new node with storage v2, you will not be able to use it with storage v1, and vice versa.
  • Reth 2.0 includes engine backpressure. This is a safeguard that prevents unbounded growth of in-memory blocks buffer in cases when persistence is not able to keep up with the chain. When the gap between canonical tip and the last persisted block exceeds --engine.persistence-backpressure-threshold (default: 16), no new payloads are executed until persistence advances. For SDK users, TreeConfig::with_persistence_backpressure_threshold provides the same functionality.
  • reth-primitives-traits crate was moved to a separate reth-core repo, along with other supporting crates. We kept the re-exports, so it should not affect the code that uses Reth as a library. If you depend on reth-primitives-traits directly, you need to switch to crates.io.
  • ExEx WAL encoding was changed from bincode to RLP for block serialization.

Dependencies

Compatible versions:

revm: 36.0.0 alloy-*: 1.8.2 alloy-evm: 0.30.0 revm-inspectors: 0.36.0

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Priority
Payload Builders High
Non-Payload Builders High

See Update Priorities for more information about this table.

Breaking Changes

SDK

... (truncated)

Changelog

Sourced from reth-ethereum-forks's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

  • Create a new branch (e.g. release/vx.y.z) and open a pull request for it
  • Ensure all tests and lints pass for the chosen commit
  • Version bump
    • Update the version in all Cargo.toml's
  • Commit the changes
    • The message format should be release: vx.y.z, substituting x.y.z for the semver.
  • The PR should be reviewed to see if anything was missed
  • Once reviewed, merge the PR

Releasing

  • Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
  • Push the tag (git push origin vx.y.z)[^1]
  • Update Homebrew Tap
  • Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
    • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

  • A summary of the release (highlights etc.)
  • The update priority (see below)
  • An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits
  • eb4c15e chore: remove changelog workflow and .changelog directory (#23376)
  • 9320216 chore: 2.0 release branch (#23372)
  • 01d851c fix: unmount schelk volume before recover in snapshot script (#23371)
  • 2155fb7 chore: added block_access_list_raw rpc (#23363)
  • a539daf feat(trie): add DecodedMultiProofV2::from_witness constructor (#23362)
  • 6b176ab feat: expose EVM config on EthTransactionValidator (#23369)
  • 0e4f143 feat: catch-up for read-only ProviderFactorys (#23357)
  • 1a72883 chore(deps): weekly cargo update (#23359)
  • adc9601 refactor(rocksdb): use secondary instances for read only providers (#23346)
  • f3e813c fix(ci): fix Grafana URL year-2082 when ABBA disabled (#23348)
  • Additional commits viewable in compare view

Updates reth-ethereum-primitives from v1.10.2 to v2.0.0

Release notes

Sourced from reth-ethereum-primitives's releases.

Reth v2.0.0

Dark (Banner)

Read our Blog Post

Reth 2.0 is a major release that makes Storage V2 the default for all new nodes, introduces the SparseTrieCacheTask for dramatically faster state root computation, and delivers across-the-board performance improvements to the engine, RPC, and P2P layers. This release also removes the deprecated reth-primitives crate and removes RocksDB feature gates (RocksDB is now always available).

Storage v2

Storage v2 is now the default for new nodes (#22890). Existing storage v1 nodes are unaffected and will continue to work.

For v2 snapshots, check out our renovated portal https://snapshots.reth.rs/.

We recommend downloading the snapshots with the --resumable flag, this will be enabled by default in the next release.

[!NOTE] Support for storage v1 nodes will be removed in a future version. An exact deprecation date will be communicated separately, all users are strongly encouraged to switch to storage v2.

[!IMPORTANT] If you rely on out-of-process database access concurrently with a running reth node (e.g. out of process block builders), with storage v2 holding a long read transaction might result in persistence stall if a reorg happens at the same time. In combination with engine backpressure this might cause the node to stall if the external reader holds the read transaction for too long.

Backwards Compatibility

  • If you start a new node with storage v2, you will not be able to use it with storage v1, and vice versa.
  • Reth 2.0 includes engine backpressure. This is a safeguard that prevents unbounded growth of in-memory blocks buffer in cases when persistence is not able to keep up with the chain. When the gap between canonical tip and the last persisted block exceeds --engine.persistence-backpressure-threshold (default: 16), no new payloads are executed until persistence advances. For SDK users, TreeConfig::with_persistence_backpressure_threshold provides the same functionality.
  • reth-primitives-traits crate was moved to a separate reth-core repo, along with other supporting crates. We kept the re-exports, so it should not affect the code that uses Reth as a library. If you depend on reth-primitives-traits directly, you need to switch to crates.io.
  • ExEx WAL encoding was changed from bincode to RLP for block serialization.

Dependencies

Compatible versions:

revm: 36.0.0 alloy-*: 1.8.2 alloy-evm: 0.30.0 revm-inspectors: 0.36.0

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Priority
Payload Builders High
Non-Payload Builders High

See Update Priorities for more information about this table.

Breaking Changes

SDK

... (truncated)

Changelog

Sourced from reth-ethereum-primitives's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

  • Create a new branch (e.g. release/vx.y.z) and open a pull request for it
  • Ensure all tests and lints pass for the chosen commit
  • Version bump
    • Update the version in all Cargo.toml's
  • Commit the changes
    • The message format should be release: vx.y.z, substituting x.y.z for the semver.
  • The PR should be reviewed to see if anything was missed
  • Once reviewed, merge the PR

Releasing

  • Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
  • Push the tag (git push origin vx.y.z)[^1]
  • Update Homebrew Tap
  • Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
    • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

  • A summary of the release (highlights etc.)
  • The update priority (see below)
  • An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits
  • eb4c15e chore: remove changelog workflow and .changelog directory (#23376)
  • 9320216 chore: 2.0 release branch (#23372)
  • 01d851c fix: unmount schelk volume before recover in snapshot script (#23371)
  • 2155fb7 chore: added block_access_list_raw rpc (#23363)
  • a539daf feat(trie): add DecodedMultiProofV2::from_witness constructor (#23362)
  • 6b176ab feat: expose EVM config on EthTransactionValidator (#23369)
  • 0e4f143 feat: catch-up for read-only ProviderFactorys (#23357)
  • 1a72883 chore(deps): weekly cargo update (#23359)
  • adc9601 refactor(rocksdb): use secondary instances for read only providers (#23346)
  • f3e813c fix(ci): fix Grafana URL year-2082 when ABBA disabled (#23348)
  • Additional commits viewable in compare view

Updates reth-evm from v1.10.2 to v2.0.0

Release notes

Sourced from reth-evm's releases.

Reth v2.0.0

Dark (Banner)

Read our Blog Post

Reth 2.0 is a major release that makes Storage V2 the default for all new nodes, introduces the SparseTrieCacheTask for dramatically faster state root computation, and delivers across-the-board performance improvements to the engine, RPC, and P2P layers. This release also removes the deprecated reth-primitives crate and removes RocksDB feature gates (RocksDB is now always available).

Storage v2

Storage v2 is now the default for new nodes (#22890). Existing storage v1 nodes are unaffected and will continue to work.

For v2 snapshots, check out our renovated portal https://snapshots.reth.rs/.

We recommend downloading the snapshots with the --resumable flag, this will be enabled by default in the next release.

[!NOTE] Support for storage v1 nodes will be removed in a future version. An exact deprecation date will be communicated separately, all users are strongly encouraged to switch to storage v2.

[!IMPORTANT] If you rely on out-of-process database access concurrently with a running reth node (e.g. out of process block builders), with storage v2 holding a long read transaction might result in persistence stall if a reorg happens at the same time. In combination with engine backpressure this might cause the node to stall if the external reader holds the read transaction for too long.

Backwards Compatibility

  • If you start a new node with storage v2, you will not be able to use it with storage v1, and vice versa.
  • Reth 2.0 includes engine backpressure. This is a safeguard that prevents unbounded growth of in-memory blocks buffer in cases when persistence is not able to keep up with the chain. When the gap between canonical tip and the last persisted block exceeds --engine.persistence-backpressure-threshold (default: 16), no new payloads are executed until persistence advances. For SDK users, TreeConfig::with_persistence_backpressure_threshold provides the same functionality.
  • reth-primitives-traits crate was moved to a separate reth-core repo, along with other supporting crates. We kept the re-exports, so it should not affect the code that uses Reth as a library. If you depend on reth-primitives-traits directly, you need to switch to crates.io.
  • ExEx WAL encoding was changed from bincode to RLP for block serialization.

Dependencies

Compatible versions:

revm: 36.0.0 alloy-*: 1.8.2 alloy-evm: 0.30.0 revm-inspectors: 0.36.0

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Priority
Payload Builders High
Non-Payload Builders High

See Update Priorities for more information about this table.

Breaking Changes

SDK

... (truncated)

Changelog

Sourced from reth-evm's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

  • Create a new branch (e.g. release/vx.y.z) and open a pull request for it
  • Ensure all tests and lints pass for the chosen commit
  • Version bump
    • Update the version in all Cargo.toml's
  • Commit the changes
    • The message format should be release: vx.y.z, substituting x.y.z for the semver.
  • The PR should be reviewed to see if anything was missed
  • Once reviewed, merge the PR

Releasing

  • Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
  • Push the tag (git push origin vx.y.z)[^1]
  • Update Homebrew Tap
  • Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
    • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

  • A summary of the release (highlights etc.)
  • The update priority (see below)
  • An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits
  • eb4c15e chore: remove changelog workflow and .changelog directory (#23376)
  • 9320216 chore: 2.0 release branch (#23372)
  • 01d851c fix: unmount schelk volume before recover in snapshot script (#23371)
  • 2155fb7 chore: added block_access_list_raw rpc (#23363)
  • a539daf feat(trie): add DecodedMultiProofV2::from_witness constructor (#23362)
  • 6b176ab feat: expose EVM config on EthTransactionValidator (#23369)
  • 0e4f143 feat: catch-up for read-only ProviderFactorys (#23357)
  • 1a72883 chore(deps): weekly cargo update (#23359)
  • adc9601 refactor(rocksdb): use secondary instances for read only providers (#23346)
  • f3e813c fix(ci): fix Grafana URL year-2082 when ABBA disabled (#23348)
  • Additional commits viewable in compare view

Updates reth-evm-ethereum from v1.10.2 to v2.0.0

Release notes

Sourced from reth-evm-ethereum's releases.

Reth v2.0.0

Dark (Banner)

Read our Blog Post

Reth 2.0 is a major release that makes Storage V2 the default for all new nodes, introduces the SparseTrieCacheTask for dramatically faster state root computation, and delivers across-the-board performance improvements to the engine, RPC, and P2P layers. This release also removes the deprecated reth-primitives crate and removes RocksDB feature gates (RocksDB is now always available).

Storage v2

Storage v2 is now the default for new nodes (#22890). Existing storage v1 nodes are unaffected and will continue to work.

For v2 snapshots, check out our renovated portal https://snapshots.reth.rs/.

We recommend downloading the snapshots with the --resumable flag, this will be enabled by default in the next release.

[!NOTE] Support for storage v1 nodes will be removed in a future version. An exact deprecation date will be communicated separately, all users are strongly encouraged to switch to storage v2.

[!IMPORTANT] If you rely on out-of-process database access concurrently with a running reth node (e.g. out of process block builders), with storage v2 holding a long read transaction might result in persistence stall if a reorg happens at the same time. In combination with engine backpressure this might cause the node to stall if the external reader holds the read transaction for too long.

Backwards Compatibility

  • If you start a new node with storage v2, you will not be able to use it with storage v1, and vice versa.
  • Reth 2.0 includes engine backpressure. This is a safeguard that prevents unbounded growth of in-memory blocks buffer in cases when persistence is not able to keep up with the chain. When the gap between canonical tip and the last persisted block exceeds --engine.persistence-backpressure-threshold (default: 16), no new payloads are executed until persistence advances. For SDK users, TreeConfig::with_persistence_backpressure_threshold provides the same functionality.
  • reth-primitives-traits crate was moved to a separate reth-core repo, along with other supporting crates. We kept the re-exports, so it should not affect the code that uses Reth as a library. If you depend on reth-primitives-traits directly, you need to switch to crates.io.
  • ExEx WAL encoding was changed from bincode to RLP for block serialization.

Dependencies

Compatible versions:

revm: 36.0.0 alloy-*: 1.8.2 alloy-evm: 0.30.0 revm-inspectors: 0.36.0

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Priority
Payload Builders High
Non-Payload Builders High

See Update Priorities for more information about this table.

Breaking Changes

SDK

... (truncated)

Changelog

Sourced from reth-evm-ethereum's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

  • Create a new branch (e.g. release/vx.y.z) and open a pull request for it
  • Ensure all tests and lints pass for the chosen commit
  • Version bump
    • Update the version in all Cargo.toml's
  • Commit the changes
    • The message format should be release: vx.y.z, substituting x.y.z for the semver.
  • The PR should be reviewed to see if anything was missed
  • Once reviewed, merge the PR

Releasing

  • Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
  • Push the tag (git push origin vx.y.z)[^1]
  • Update Homebrew Tap
  • Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
    • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

  • A summary of the release (highlights etc.)
  • The update priority (see below)
  • An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits
  • eb4c15e chore: remove changelog workflow and .changelog directory (#23376)
  • 9320216 chore: 2.0 release branch (#23372)
  • 01d851c fix: unmount schelk volume before recover in snapshot script (#23371)
  • 2155fb7 chore: added block_access_list_raw rpc (#23363)
  • a539daf feat(trie): add DecodedMultiProofV2::from_witness constructor (#23362)
  • 6b176ab feat: expose EVM config on EthTransactionValidator (#23369)
  • 0e4f143 feat: catch-up for read-only ProviderFactorys (#23357)
  • 1a72883 chore(deps): weekly cargo update (#23359)
  • adc9601 refactor(rocksdb): use secondary instances for read only providers (#23346)
  • f3e813c fix(ci): fix Grafana URL year-2082 when ABBA disabled (#23348)
  • Additional commits viewable in compare view

Updates reth-network-peers from 8e3b5e6 to eb4c15e

Commits
  • eb4c15e chore: remove changelog workflow and .changelog directory (#23376)
  • 9320216 chore: 2.0 release branch (#23372)
  • 01d851c fix: unmount schelk volume before recover in snapshot script (#23371)
  • 2155fb7 chore: added block_access_list_raw rpc (#23363)
  • a539daf feat(trie): add DecodedMultiProofV2::from_witness constructor (#23362)
  • 6b176ab feat: expose EVM config on EthTransactionValidator (#23369)
  • 0e4f143 feat: catch-up for read-only ProviderFactorys (#23357)
  • 1a72883 chore(deps): weekly cargo update (#23359)
  • adc9601 refactor(rocksdb): use secondary instances for read only providers (#23346)
  • f3e813c fix(ci): fix Grafana URL year-2082 when ABBA disabled (#23348)
  • Additional commits viewable in compare view

Updates reth-revm from v1.10.2 to v2.0.0

Release notes

Sourced from reth-revm's releases.

Reth v2.0.0

Dark (Banner)

Read our Blog Post

Reth 2.0 is a major release that makes Storage V2 the default for all new nodes, introduces the SparseTrieCacheTask for dramatically faster state root computation, and delivers across-the-board performance improvements to the engine, RPC, and P2P layers. This release also removes the deprecated reth-primitives crate and removes RocksDB feature gates (RocksDB is now always available).

Storage v2

Storage v2 is now the default for new nodes (#22890). Existing storage v1 nodes are unaffected and will continue to work.

For v2 snapshots, check out our renovated portal https://snapshots.reth.rs/.

We recommend downloading the snapshots with the --resumable flag, this will be enabled by default in the next release.

[!NOTE] Support for storage v1 nodes will be removed in a future version. An exact deprecation date will be communicated separately,...

Description has been truncated

@dependabot
build(deps): bump the reth group across 1 directory with 9 updates
92c651c 
Bumps the reth group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [reth-chainspec](https://github.com/paradigmxyz/reth) | `v1.10.2` | `v2.0.0` |
| [reth-errors](https://github.com/paradigmxyz/reth) | `v1.10.2` | `v2.0.0` |
| [reth-ethereum-forks](https://github.com/paradigmxyz/reth) | `v1.10.2` | `v2.0.0` |
| [reth-ethereum-primitives](https://github.com/paradigmxyz/reth) | `v1.10.2` | `v2.0.0` |
| [reth-evm](https://github.com/paradigmxyz/reth) | `v1.10.2` | `v2.0.0` |
| [reth-evm-ethereum](https://github.com/paradigmxyz/reth) | `v1.10.2` | `v2.0.0` |
| [reth-revm](https://github.com/paradigmxyz/reth) | `v1.10.2` | `v2.0.0` |



Updates `reth-chainspec` from v1.10.2 to v2.0.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

Updates `reth-errors` from v1.10.2 to v2.0.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

Updates `reth-ethereum-forks` from v1.10.2 to v2.0.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

Updates `reth-ethereum-primitives` from v1.10.2 to v2.0.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

Updates `reth-evm` from v1.10.2 to v2.0.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

Updates `reth-evm-ethereum` from v1.10.2 to v2.0.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

Updates `reth-network-peers` from `8e3b5e6` to `eb4c15e`
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

Updates `reth-revm` from v1.10.2 to v2.0.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

Updates `reth-trie-common` from `8e3b5e6` to `eb4c15e`
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Commits](paradigmxyz/reth@8e3b5e6...eb4c15e)

---
updated-dependencies:
- dependency-name: reth-chainspec
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-errors
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-ethereum-forks
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-ethereum-primitives
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-evm
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-evm-ethereum
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-network-peers
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-revm
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-trie-common
  dependency-version: eb4c15e5e36d8776d46629beae4c0a69af7ab04f
  dependency-type: direct:production
  dependency-group: reth
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants