Skip to content

Bump op-reth to v2.9.0 - #32

Open
dfuse-bot wants to merge 53 commits into
release/op-reth-2.xfrom
bump/op-reth-2.9.0
Open

dfuse-bot wants to merge 53 commits into
release/op-reth-2.xfrom
bump/op-reth-2.9.0

Conversation

@dfuse-bot

@dfuse-bot dfuse-bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Merges upstream op-reth/v2.9.0 (50 commits on top of op-reth/v2.8.2) into release/op-reth-2.x. To be tagged op-reth-v2.9.0-fh3.1 once merged (the tag the release tracker proposed, which follows the naming rule). The Firehose block model is unchanged, so the version stays fh3.1.

Before merging

  • Merge op-v2.7.0-0 for op-reth v2.9.0 reth#103 is merged with a merge commit and its head is still f965b380132b5a770e2a6cfaf3e8d9f68076f380, the commit rust/Cargo.toml pins (it will be tagged op-reth-v2.9.0-fh3.1 in streamingfast/reth).

Merge order: streamingfast/reth#103 first, then this PR.

What changed

  • Upstream: reth moves to ethereum-optimism/reth op-v2.7.0-0 (reth v2.7.0), revm to 43.0.3, alloy 2.5. Upstream's release notes list breaking RPC changes (--rpc.gascap now caps eth_estimateGas, three RPC limit flags reject 0, error code 4444 for pruned history), lower RPC cache defaults and the sepolia-devnet-4/5/6 chain configs.
  • Reth pin: streamingfast/reth commit f965b380 (Merge op-v2.7.0-0 for op-reth v2.9.0 reth#103, future tag op-reth-v2.9.0-fh3.1), which merges op-v2.7.0-0 into release/optimism-2.x. It also brings in the post-exec (0x7D) transaction mapping from Trace Optimism post-exec transactions reth#92, which no release had pinned yet. firehose-tracer moves to 5.5.1.
  • alloy-evm: stays at 0.39, so the streamingfast/evm v0.39.0-sf patch is unchanged.
  • Conflicts: rust/Cargo.toml (upstream reindented it; rebuilt from upstream's file with our reth pins, firehose-tracer, the Firehose crate and the alloy-evm patch), rust/Cargo.lock (upstream's lock re-resolved), and rust/op-reth/crates/trie/src/engine/tasks/execute_block.rs (kept execute_one so the proofs ExEx never prints a second FIRE BLOCK, on top of upstream's new into_evm_state_provider()).
  • Build fixes: op-reth/crates/firehose/src/engine_validator.rs (our copy of reth's payload validator) and the built-block trace in op-reth/crates/payload/src/builder.rs now read state through reth's EvmStateProvider, like the upstream code they follow.
  • Also ships the unreleased proofs ExEx fix already on release/op-reth-2.x (Stop proofs ExEx from printing Firehose blocks #31).

Firehose review

  • Serial tracing order: no new parallel or out-of-order execution on the traced path. The sender recovery cache that reth v2.7.0 enables by default keeps transaction order, and OP blocks never carry a block access list, so the BAL parallel path is never taken.
  • Block printed after validation: the OP engine validator still prints the traced block only after state root and post-execution checks. Upstream's OP post-execution validation copy only changes its mirror comment.
  • Fee vault formulas: extras.rs recomputes the OP fee vault credits. In this range, op-revm handler.rs, alloy-op-evm and reth-optimism-evm change only comments and test plumbing, so the formulas are unchanged.
  • RPC replays: upstream now replays debug_trace*/trace_* (and the new Lagoon SDM settlement replay) through executor_for_block. OpFirehoseEvmConfig only hooks batch_executor, so RPC calls never print blocks.
  • Activations (ACTIVATIONS.md): op-reth v2.9.0 defines no new OpHardfork. Its superchain-registry update only adds the three Sepolia devnets; the OP Mainnet and Unichain fork times are unchanged. Lagoon is still unscheduled in the code; Optimism's public notice now targets January 11, 2027. The ACTIVATIONS.md Lagoon row now lists what Lagoon changes in the Firehose block (see Open questions).

Dependencies

  • Pins: streamingfast/reth release/optimism-2.x (new PR Merge op-v2.7.0-0 for op-reth v2.9.0 reth#103) and streamingfast/evm release/0.x (unchanged, no PR needed). The dependency table in the release tracker is correct.
  • Pinned by: no StreamingFast repository pins this fork apart from the deployment repository (code search for op-reth-v2.8.2-fh3.1).

CHANGELOG

## op-reth-v2.9.0-fh3.1

Bumps the SF op-reth fork to upstream `op-reth/v2.9.0` (50 upstream commits on top of
`op-reth/v2.8.2`).

### Changed

* Merged upstream `op-reth/v2.9.0`, which moves reth to ethereum-optimism/reth `op-v2.7.0-0`
  (reth v2.7.0) and revm to 43.0.3. Upstream's release notes list breaking RPC changes
  (`--rpc.gascap` now caps `eth_estimateGas`, three RPC limit flags reject `0`, error code `4444`
  for pruned history) and lower RPC cache defaults. The fee vault formulas, deposit handling and
  fork schedule the Firehose hooks depend on are unchanged.
* Reth now comes from `streamingfast/reth` `op-reth-v2.9.0-fh3.1`, which merges `op-v2.7.0-0` into
  `release/optimism-2.x`. `alloy-evm` stays on `streamingfast/evm` `v0.39.0-sf`.
* `firehose-tracer` moves to 5.5.1.
* `ACTIVATIONS.md` records the January 11, 2027 target for Lagoon and what its post-exec
  transaction and gas refunds change in the Firehose block.

### Fixed

* Optimism post-exec transactions (type `0x7D`, enabled by Lagoon) are traced as
  `TRX_TYPE_OPTIMISM_POST_EXEC` instead of stopping the node.
* With `--proofs-history`, the proofs ExEx no longer prints a second `FIRE BLOCK` for each block
  it re-executes to build its proof storage. [...]

Open questions

  • Lagoon (not scheduled yet, targeted for January 11, 2027). With this release the node no longer panics on the 0x7D post-exec transaction. The Firehose output for Lagoon blocks still needs a decision before activation. No Battlefield devnet activates Lagoon, so none of this is tested:

    1. The block executor short-circuits the 0x7D transaction without running the EVM, so its trace has no call. The tracer then drops its receipt and leaves its status unknown.
    2. OpPostTxExtras runs for that transaction too and reads the previous transaction's environment. The fee vault change it computes is discarded with the empty transaction, but it uses up a block ordinal.
    3. With post-exec (SDM settlement) refunds, the coinbase and fee vault credits match the net state change, but the sender's GasRefund leaves out the operator fee part of the refund when operator fees are nonzero. The same may already apply to the Isthmus operator fee refund from reimburse_caller; this was not confirmed. The Battlefield devnet runs with zero operator fee parameters, so it does not cover it either.

    I left these unchanged. Someone should compare them with what op-geth's tracer emits and decide on the model.

Test Execution Summary

Build Status

  • streamingfast/reth cargo check --workspace --all-targets: PASSED
  • streamingfast/optimism rust/: cargo check --workspace --all-targets: PASSED
  • streamingfast/optimism rust/: cargo build --release -p op-reth --bin op-reth: PASSED

Unit Tests

Repository Package Status Notes
streamingfast/reth reth-firehose PASSED 34 tests
streamingfast/reth reth-firehose-tests (prestate golden files) PASSED 2 tests, golden files unchanged
streamingfast/reth reth-engine-tree --test firehose_live_tracing PASSED 1 test
streamingfast/optimism reth-optimism-firehose PASSED no unit tests in the crate
streamingfast/optimism op-alloy-consensus --features firehose PASSED 106 tests
streamingfast/optimism reth-optimism-evm PASSED 58 tests
streamingfast/optimism reth-optimism-payload-builder PASSED 45 tests
streamingfast/optimism reth-optimism-trie (lib, tests/lib.rs, tests/live.rs) PASSED 254 + 86 + 8 tests, with --test-threads=4 (see notes)
streamingfast/optimism reth-optimism-node --test it builder PASSED 2 tests

Notes:

  • reth-optimism-trie with the default 60 test threads failed 88 tests with MDBX Cannot allocate memory (12) when opening their test databases, all at once. With --test-threads=4 all pass, so this is the test machine, not the merge.
  • The build image ships builder-playground v0.3.3-sf1; the OP devnet needs v0.3.3-sf2 (--sequencer-el, --enable-karst), built from source for this run.
  • reth v2.7.0 locks llvm-sys 221 (LLVM 22). The build machine has LLVM 23 only; it builds with LLVM_SYS_221_PREFIX=/usr/lib/llvm-23 and LLVM 23's llvm-config first on PATH.

Integration Tests

  • Status: NOT RUN (no integration suite beyond the tests above for this chain)

Battlefield Tests

  • Status: PASSED
  • Pass/Fail: 95 passing / 0 failing (43 pending: the Amsterdam, ArbOS, Base and other suites that do not apply to an OP Stack chain)
  • Compare blocks (Firehose blocks against the node's JSON-RPC): PASSED
  • Karst suite (activation block upgrade deposits, CLZ, MODEXP, P256VERIFY, BN254 pairing cap, transaction gas cap): PASSED
  • No panic or error in the Firehose op-reth log.
  • Failures: none.
  • Coverage: the devnet runs Jovian from genesis and Karst from L2 block 10, so every fork live on OP Mainnet and Unichain is covered. Operator fee parameters are zero, so the OperatorFeeVault credit is not exercised. Lagoon (not scheduled yet) is not activated by any Battlefield devnet.

Commands (battlefield-ethereum adb1921, builder-playground v0.3.3-sf2 built from source, op-node v1.19.11, fireeth v2.24.1, op-reth from cargo build --release -p op-reth --bin op-reth on this branch):

./scripts/optimism/run_optimism_devnet.sh
./scripts/run_firehose_op_reth_devnet.sh   # op-reth from this branch first on PATH
pnpm test:fh3.0:op-reth-devnet

mds1 and others added 30 commits November 9, 2026 13:55
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ts (ethereum-optimism#24008)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…m-optimism#24001)

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
…ll tests (ethereum-optimism#24021)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…4015)

Co-authored-by: wwared <541936+wwared@users.noreply.github.com>
…eum-optimism#23664)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…optimism#24032)

Co-authored-by: yoshidan <naohiro.y@gmail.com>
Co-authored-by: wwared <541936+wwared@users.noreply.github.com>
…replay (ethereum-optimism#23942)

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ript (ethereum-optimism#23999)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…thereum-optimism#23665)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…gnatures (ethereum-optimism#23977)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
…ilds (ethereum-optimism#24002)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…-optimism#23946)

Co-authored-by: Lake <258745035+lake-dunamu@users.noreply.github.com>
… L1s (ethereum-optimism#24022)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
mds1 and others added 23 commits November 10, 2026 22:07
…es nightly (ethereum-optimism#24037)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…sm#24016)

Co-authored-by: wwared <541936+wwared@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Adrian Sutton <adrian@oplabs.co>
… files in JUnit (ethereum-optimism#24056)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…zz test (ethereum-optimism#24058)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…sm#23862)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…loyments on forge (ethereum-optimism#23666)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…reum-optimism#23667)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ons (ethereum-optimism#24064)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ancestors (ethereum-optimism#23960)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The engine validator copy and the built-block trace now read state through
reth's EvmStateProvider, like the upstream code they follow.
ACTIVATIONS.md now records the January 2027 Lagoon target and what its
post-exec transaction and refunds change in the Firehose block.
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.