chore(deps): bump reth-transaction-pool from v2.1.0 to v2.2.0

[dependabot]

Bumps reth-transaction-pool from v2.1.0 to v2.2.0.

Release notes

Sourced from reth-transaction-pool's releases.

Reth v2.2.0

This release lays the groundwork for Amsterdam (EIP-7928 Block Access Lists), introducing a BAL store abstraction, P2P wire support for fetching BALs alongside full blocks, payload-builder integration, and parallel/batched BAL execution paths. It also enables Discv5 by default, adds snap/2 wire helpers, and bounds the memory footprint of the P2P transaction manager and network channels. Numerous performance improvements land in the trie, database, and re-execution paths, alongside a broad set of correctness fixes in the engine, RPC, networking, and CLI layers.

Action Required: Discv5 is now enabled by default (#23686). If you previously relied on Discv4-only behaviour, review your CLI/config flags. BAL parallel execution and storage prefetch are gated behind CLI flags and are off by default (#23764, #23770).

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.2.x, please downgrade to v2.1.0.

Update Priority

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

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

See Update Priorities for more information about this table.

Features

Engine & Payload

• Suppress persistence during payload building to reduce contention (#23618)
• Enabled BAL building in the Ethereum payload builder (#23597)
• New CLI flag to disable BAL storage prefetch (#23770)
• Added DecodedBal to ExecutionEnv (#23675)

P2P / Networking

• Discv5 is now enabled by default (#23686)
• Support binding Discv5 and Discv4 to the same port (#23613)
• Customizable discovery defaults (#23843)
• Memory-bounded channel between network and transaction manager (#23802)
• Bound memory footprint of P2P messages (#23718)
• Avoid RLP-decoding NewBlock payloads to save CPU (#23712)
• Added snap/2 wire helpers and messages (#23611)
• Optionally fetch BAL with full blocks over P2P (#23629)
• Added BAL requirement to block access list requests (#23682)
• Enforce BAL response soft limit (#23725)
• Added basic in-memory BAL store (#23710)
• Added BAL request e2e coverage (#23727)
• Scaffolded BAL store abstraction (#23596)

Performance

... (truncated)

Changelog

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

• 88505c7 fix(re-execute): properly handle selfdestructed storage slots (#23832)
• c14bc59 chore: release 2.2.0 (#23831)
• 347c132 fix: skip move_to_static_files for storage.v2 (#23814)
• 5f85eb7 feat(engine): add getBlobsV4 endpoint (#23767)
• a12454d perf(db): prebind cursor operation metrics (#23654)
• c194c17 chore(deps): bump alloy to 2.0.4 (#23828)
• 43a7452 fix(rpc): narrow getLogs retry range (#23818)
• 73ec2c9 docs(engine): clarify BAL storage prefetch flag (#23815)
• 76e8865 ci(hive): update amsterdam fixtures and branch (#23807)
• ad08829 feat: introduce memory-bound channel for network<->tx manager messages (#23802)
• 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)

[dependabot]

Labels

The following labels could not be found: dependencies, rust. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.