chore(deps): bump reth-primitives from v1.1.0 to v1.2.0

[dependabot]

Bumps reth-primitives from v1.1.0 to v1.2.0.

Release notes

Sourced from reth-primitives's releases.

Reth v1.2.0

Pectra

This release is Pectra ready and includes timestamps for the upcoming Holesky and Sepolia hardforks.

Network	Timestamp
Holesky	Feb 24 2025 21:55:12 GMT
Sepolia	Mar 05 2025 07:29:36 GMT

--engine.legacy deprecation

As announced in v1.1.5, this release fully removes support for the --engine.legacy option.

Users that rely on the legacy behaviour where blocks are immediately flushed to disk should run with --engine.persistence-threshold 0 and --engine.memory-block-buffer-target 0 to restore that behaviour.

Gas Limit increase

Default suggested gas limit is now 36M: paradigmxyz/reth#13318

Performance

This release includes a new State Root Task and Sparse Trie data structure that improve the state root computation performance, and it’s enabled by default for all users.

It reduces the engine_newPayload call latencies by up to 50%. The average 99th percentile response time has been reduced from 120ms to 80ms. This work is part of ongoing improvements that will be rolled out in upcoming releases.

For more technical details on how the new design works, see https://github.com/paradigmxyz/reth/blob/main/crates/engine/tree/docs/root.md.

We’re going to be implementing more optimizations & testing, and then roll this out on OP Stack L2s for all OP-Reth users by default as well.

OP Stack

• This release contains some preparations for the upcoming Isthmus hardfork, but is not yet Isthmus ready.
• Includes support for forwarding sendRawTransactionConditional to the sequencer.

Reth as a library

This release introduces new top level meta crates for easier Reth dependency management:

• reth_ethereum re-exports various commonly used Ethereum and Reth specific types, such as primitives, node components, RPC…
• reth_op re-exports various commonly used Optimism and Reth specific types, such as primitives, node components, RPC…

Primitives

This contains several breaking API changes surrounding primitive types.

... (truncated)

Changelog

Sourced from reth-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 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 is 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

• 1e965ca fix(ci): docker release (#14458)
• f56f633 chore(ci): update hive expected failures (#14454)
• 1e0b0d8 chore: release v1.2.0 (#14438)
• f0530a7 feat: add Block::seal (#14451)
• 4f73e1a chore: remove BatchExecutor (#14453)
• 1970a44 fix(trie): reveal blinded sparse trie when calculating root (#14449)
• 172369a feat: add Consensus to ExecutionStage (#14447)
• 3e07d65 feat(grafana): add block validation overhead graph (#14431)
• bb67c0e fix(grafana): use correct datasource for all metrics (#14432)
• 71b9f12 feat(op, cli): add cli option to enable tx conditional (#14421)
• 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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.5%. Comparing base (54f28c3) to head (44e552d).

❗ There is a different number of reports uploaded between BASE (54f28c3) and HEAD (44e552d). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (54f28c3)	HEAD (44e552d)
	4	3

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[refcell]

yea these are gonna break because the MSRV of reth at v1.2 is 1.82 and we are set to 1.81. I believe succinct had ask us not to bump this again so we should confirm with them before bumping or at least get a release out before bumping.
good suggestion tho dependabot