chore(deps): bump reth-db-api from v1.6.0 to v1.10.0

[dependabot]

Bumps reth-db-api from v1.6.0 to v1.10.0.

Release notes

Sourced from reth-db-api's releases.

Reth v1.10.0

This release brings performance improvements (overlay caching for state providers (#19752), transaction pool optimizations (#20405, #20398)), new RPC endpoints (engine_getBlobsV3, debug_getBadBlock, reth_subscribePersistedBlock, testing_buildBlockV1). With these changes we saw a ~25% improvement on average on newPayload.

Further, the release comes with CLI enhancements (--netrestrict, --max-peers, --minimal, --p2p-secret-key-hex), and extended OP Stack flashblock support. This is a major version bump due to SDK breaking changes including the removal of the Consensus::Error associated type and revamped tx policy traits.

Action Required: The merkle changeset defaults were fixed, but this means if you had manually set a non-default value, it may now conflict or behave unexpectedly. Users that are running a non default (1064) merkle changeset pruning distance should remove it from their reth.toml (#20108)

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 1.10.x, please downgrade to 1.9.4

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

Breaking Changes

SDK

• Removed associated error type for Consensus trait (#20843)
• Revamped tx policy traits (#19878)
• Extended tx policy API (#20861)
• Changed BestTransactions::mark_invalid to accept error by reference (#19981)
• Replaced CliHeader with HeaderMut (#20001)
• Changed append_block_body to take a ref (#20504)
• EthExecutionContext requires extradata (#20314)
• Renamed tx_resp_builder (#20037)

Pruning Behavior

• Fixed merkle changeset defaults (#20108): Action Required - Users running a non-default (1064) merkle changeset pruning distance should remove it from their reth.toml

Features

Performance

• Cache overlays in the OverlayStateProviderFactory (#19752)
• Improve txpool updates (#20405, #20398)

RPC

... (truncated)

Changelog

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

• b25f32a chore(release): set version v1.10.0 (#21091)
• 905de96 chore: release 1.9.4 (#21048)
• 27fbd9a fix(db): change commit return type from Result<bool> to Result<()> (#21077)
• 26a99ac perf: small improvement to extend_sorted_vec (#21032)
• 1265a89 refactor: make use of dbi consistent across mdbx interface (#21079)
• b9ff594 feat(primitives): add SealedBlock::decode_sealed for efficient RLP decoding (...
• a75a0a5 feat(cli): support file:// URLs in reth download (#21026)
• 0a4bac7 feat(primitives): add From<Sealed> for SealedBlock<B> (#21078)
• 1fbd5a9 feat: Support for sending logs through OTLP (#21039)
• 1bc07fa perf: use binary search in ForwardInMemoryCursor (#21049)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[wiz-b4c72f16a4]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	4
Sensitive Data	-
Secrets	-
IaC Misconfigurations	-
SAST Findings	-
Software Management Findings	-
Total	4

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.