chore(deps): bump reth-provider from v1.9.3 to v1.11.0

[dependabot]

Bumps reth-provider from v1.9.3 to v1.11.0.

Release notes

Sourced from reth-provider's releases.

Reth v1.11.0

Reth v1.11.0 delivers massive state root performance gains, benchmarks show a ~25% reduction in mean newPayload latency (42.9ms → 32.4ms), ~27% improvement at P90 (72.4ms → 53.1ms), and +33% throughput (700M → 1G gas/s), through the new sparse trie as cache. Up-to-date performance metrics can be seen on the ethpandaops Labs dashboard. v1.11.0 also introduces an experimental hot/cold storage architecture, introduced via --storage.v2.

The headline feature of this release is sparse trie as cache (#21583): the sparse trie is now preserved across payload validations (#21534), eliminating redundant trie reconstruction on every newPayload, and allowing reuse of trie nodes in memory. Combined with parallel proof workers pool optimizations (#22051), integration with prewarming (#21901), parallel state hashing (#21836), and many allocation/scheduling optimizations, state root computation is dramatically faster.

The new --storage.v2 CLI flag (#21868) introduces an experimental hot/cold storage architecture that routes history indices and transaction hash lookups to RocksDB, and writes changesets to static files. This architecture also drops usage of reth's plain state tables (#21115). Below is the measured disk usage at block 24396823:

Node Type	Pre v1.11	v1.11 (v2)	Savings
Full	1.46 TB	1.02 TB	-30%
Minimal	449 GB	224 GB	-50%
Archive	2.99 TB	2.31 TB	-23%

Note: --storage.v2 requires a fresh sync from scratch — it cannot be enabled on an existing node database. Public snapshots are available at snapshots.reth.rs to accelerate initial sync.

⚠️ Starting with v1.11.0, this release no longer includes vanilla op-reth binaries. op-reth has been fully removed from this repository (#21532) and now lives in its own dedicated repo. For OP Stack releases, please refer to OP Labs' announcement.

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 1.11.x, please downgrade to v1.10.2

Update Priority

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

User Class	Priority
Payload Builders	High
Non-Payload Builders	Medium

Breaking Changes

SDK

• Removed reth-stateless crate (#22115)
• Removed ress crates from workspace (#22057)
• Removed TypesAnd1-5 staging types from ProviderFactoryBuilder (#22049)
• Removed SerialSparseTrie — always use ParallelSparseTrie (#21808, #21435)
• Use hashed state as canonical state representation (#21115)
• Merged SparseTrieExt into SparseTrie trait (#22035)
• Removed op-reth from repository — it now lives in its own repo (#21532)
• Breaking dependency bumps: revm 34, alloy 1.6.3, alloy-evm 0.27.2 (#21584, #21337)
• Added Block associated type to TransactionValidator trait (#21359)

CLI

... (truncated)

Changelog

Sourced from reth-provider'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

• 564ffa5 fix(ci): pass docker tags as separate set entries in bake action (#22151)
• 12891dd chore: allow invalid storage metadata (#22150)
• c101502 chore: release reth v1.11.0 (#22148)
• e3fe632 chore(storage): rm storage settings, use only one (#22042)
• e3d520b feat(network): add inbound / outbound scopes for disconnect reasons (#22070)
• 9f29939 feat: bundle mdbx_copy as reth db copy subcommand (#22061)
• 10881d1 chore: fix book (#22142)
• 4085934 feat(download): optional chain-aware snapshot url (#22119)
• 8caf8cd docs: improve reth.rs/overview page (#22131)
• 1e8030e fix(engine): return error on updates channel disconnect in sparse trie task (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)