chore(deps): bump reth-tracing-otlp from v2.4.1 to v2.5.0

[dependabot]

Bumps reth-tracing-otlp from v2.4.1 to v2.5.0.

Release notes

Sourced from reth-tracing-otlp's releases.

Reth v2.5.0

Reth v2.5.0 improves execution performance across the board. Release regression testing against v2.4.1 measured 5-10% lower mean block-processing latency, especially in long-tail workloads.

Performance

• Added an opt-in sender recovery cache shared across transaction paths, reducing mean mainnet block-processing latency by 3%. Enable it with --engine.sender-recovery-cache (#26494).
• Added an opt-in transaction-pool prewarming to pipeline transaction ingestion with block execution, reducing mean mainnet block-processing latency by 7%. Enable it with --engine.txpool-prewarming; it is enabled by default only in nightly Docker builds (#26378, #26493).
• Avoided proof-worker cursor overlays when the sparse trie already covers the required persisted state (#25952).
• Parallelized sparse-trie pruning retention-set construction and removed unnecessary LFU retention bookkeeping (#26439).
• Removed sparse-trie memory accounting from hot paths where repeated size estimation added unnecessary work (#26458).
• Kept five recent blocks in memory by default to reduce repeated state reconstruction (#26462).
• Centralized overlay anchoring to reduce duplicate Engine and persistence work (#26580).

Update Priority

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

Breaking Changes

SDK and Storage APIs

• Reorganized storage-overlay APIs: renamed StateTrieOverlayManager to OverlayManager and moved it, OverlayBuilder, OverlayStateProvider, and OverlayStateProviderFactory to the new reth-storage-overlay crate. ChangesetCache is now internal rather than a public import (#26506, #26522, #26611).
• Changed PayloadValidator::validate_block_post_execution_with_hashed_state to take state updates by value and receive the resolved parent header. Custom validators overriding this method must update their signatures (#26398, #26420).
• Removed public changed-path tracking fields and methods from payload and sparse-trie APIs (#26403).
• Removed ConsistentDbView from reth-provider (#26581).
• Removed the reth-rpc-api-testing-util crate (#26393).

Features

Networking and P2P

• Added real snap/2 account-range, storage-range, and bytecode serving, including boundary proofs (#26339).
• Added support for discv5 ENR records in --bootnodes, --trusted-peers, and peers.trusted_nodes (#26448).
• Added bootnode configuration to reth.toml, with CLI configuration taking precedence (#26551).
• Added configurable no-op client-version handling for network connections (#26652).
• Added blob-cell availability tracking to the transaction pool (#25463).

RPC

• Added eth_getMultiProof to retrieve consolidated EIP-1186 proofs for multiple account and storage targets (#26555).
• Added debug_getRawBlockAccessList for retrieving the RLP-encoded EIP-7928 block access list (#26438).
• Reused a single EVM during block replay tracing, fixing downstream chains with block-scoped EVM state and avoiding redundant EVM construction (#26614).
• Added network-specific log response conversion for downstream chain implementations (#26491).
• Allowed execution-witness requests to use any BlockId (#26572).
• Made the testing RPC handler generic over node-specific types (#26547).

... (truncated)

Changelog

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

• 189c0df chore: bump reth version to 2.5.0
• 3a83ccc fix(eth-wire): reject out-of-range subprotocol message IDs (#26654)
• f3e49cc fix(engine): adjust payload validation (#26651)
• db9f641 feat(network): allow configuring no-op client version (#26652)
• c733889 fix(storage): tolerate unknown RocksDB column families (#26647)
• 905058c fix(storage): roll back RocksDB BAL storage (#26646)
• 62808bd fix(txpool): allow senders with empty code hash (#26644)
• 199387a chore: expose blob cell availability on pooled transactions (#26642)
• 1c6945c fix(network): do check the ECIES id in hello (#26639)
• ddb640b ci: allow transitive bitmaps advisory (#26638)
• 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: rust. Please create it before Dependabot can add it to a pull request.

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

[dependabot]

Looks like reth-tracing-otlp is up-to-date now, so this is no longer needed.