Skip to content

rust: update reth to v2.7.0 - #23156

Closed
joshklop wants to merge 12 commits into
joshklop/update-reth-v2.6.0from
joshklop/update-reth-v2.7.0
Closed

joshklop wants to merge 12 commits into
joshklop/update-reth-v2.6.0from
joshklop/update-reth-v2.7.0

Conversation

@joshklop

@joshklop joshklop commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Brings upstream execution/RPC fixes into the OP Stack, stacked on #23046 so the parent update stays independently reviewable. The fork audit found only release metadata and fork-local CI changes, so returning to the upstream release drops no runtime backport; published OP crate versions remain unchanged.

Speculative flashblocks retain an overlay on their canonical anchor rather than adopting an API that assumes the immediate parent is canonical. Independent Rust, defensive security, and partitioned full-range dependency reviews cover the upgrade; all actionable findings are fixed. Mirrors are audited: 58 current and eight intentionally frozen ports.

Operator migration notes:

  • RPC cache entry defaults fall from 5,000 to 1,000 blocks and 2,000 to 500 receipts. --rpc-cache.max-blocks 5000 --rpc-cache.max-receipts 2000 restores the entry counts, but the new 2 GiB block / 1 GiB receipt byte caps still apply; size those budgets for the workload. Idle expiry defaults to one hour; --rpc-cache.idle-timeout 0s disables expiry. Zero byte budgets disable caching, not just the byte limit.
  • Sender recovery caching is enabled by default; --engine.sender-recovery-cache=false or RETH_ENGINE_SENDER_RECOVERY_CACHE=false restores the disabled setting. Existing bare-flag usage still works. No existing flag names are removed; the snapshot also records the new backfill threshold option and clarified gas-cap help. Unsupported BAL-only options remain hidden and rejected, including the new byte limit.
  • Retain rollout checks for existing-database RocksDB BAL-column initialization and discv5 ENR advertisement. Focused speculative-overlay root/proof and failed-deposit/post-exec Parity tracing coverage remain follow-ups, not demonstrated regressions; production account-ext is not enabled.

Verification on reviewed head d669648e7f: 3,355 workspace tests passed (10 skipped), plus all nine proof core end-to-end tests against the rebuilt binary, including account/storage proofs, both witness methods, and restart/resync. Full lint, locked workspace/test compilation, node build, doctests, small-stack beacon checks, no_std, formatting and mirror checks pass. Receipt decoder, unsupported BAL option, and stored-trie regressions were verified red before their fixes and green afterward. All 77 reported CI checks pass, including ci-gate, required-contracts-ci, required-rust-ci, required-rust-e2e, and dependency-review. Source review and passing tests do not establish consensus safety.

Return to the upstream v2.7.0 release after auditing the fork-only release and CI changes. Synchronize shared REVM, Alloy, and reth-core requirements and both lockfiles.

Adapt EVM state-provider boundaries, task cancellation, witness bounds, receipts, and e2e setup. Preserve speculative flashblock pending state on its canonical anchor with a port of the removed overlay provider. Mirror canonical receipt-decoding guards with regression tests.

Audit upstream mirrors, regenerate the operator-facing CLI snapshot, and document update lessons.
@joshklop
joshklop force-pushed the joshklop/update-reth-v2.7.0 branch from 5bb55fc to d669648 Compare October 2, 2026 02:46
@joshklop
joshklop marked this pull request as ready for review October 2, 2026 16:44
@joshklop
joshklop requested a review from a team as a code owner October 2, 2026 16:44
@joshklop
joshklop marked this pull request as draft October 2, 2026 16:46
@joshklop
joshklop force-pushed the joshklop/update-reth-v2.6.0 branch from e8453a0 to 12d73f7 Compare October 10, 2026 22:11
@joshklop joshklop closed this Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant