Skip to content

Merge op-reth v2.8.2 - #30

Merged
sduchesneau merged 22 commits into
release/op-reth-2.xfrom
bump/op-reth-2.8.2
Nov 10, 2026
Merged

sduchesneau merged 22 commits into
release/op-reth-2.xfrom
bump/op-reth-2.8.2

Conversation

@dfuse-bot

Copy link
Copy Markdown

Merges upstream op-reth/v2.8.2 (18 commits on top of op-reth/v2.8.1) into release/op-reth-2.x. Release tag once merged: op-reth-v2.8.2-fh3.1 (newest tag on the branch is op-reth-v2.8.1-fh3.1; the Firehose block model is unchanged, so fh3.1 stays).

No other StreamingFast repository needs a release first: upstream changes no reth, revm, alloy-evm or op-alloy version in this range. Merge this PR with a merge commit and tag the merge commit.

What changed

  • Upstream: the interop transaction pool's endpoint.up gauge stays up when a filter answers -321100 (out of scope); the operator gas limit (OpGasLimitConfig, now in reth-optimism-txpool) is shared with the transaction pool, which starts with the chain's block gas limit; new pool admission tests; kona rollup config gains settlement_chain_id (not in the op-reth binary). The merge had no conflicts.
  • Reth and alloy-evm are now pinned by commit with the tag in a comment, on the same releases as before: streamingfast/reth 93fb772a… (op-reth-v2.8.1-fh3.1) and streamingfast/evm 52afebec… (v0.39.0-sf). The lock used to resolve the reth tag to the head of Merge ethereum-optimism/reth op-v2.6.0-2 for op-reth v2.8.1 reth#90 (1d4c8b49); it now resolves to the tagged merge commit, which has the same tree.
  • ACTIVATIONS.md: statuses refreshed for v2.8.2; Lagoon now notes Optimism's mid-December 2026 target.
  • The dependency table this run started from listed the reth and alloy-evm pins as commits; they were tags until this PR. It listed nothing that pins this fork, which gh search code confirms apart from the deployment configuration.

Operator-visible changes from upstream

  • The transaction pool rejects transactions above the operator gas limit when one is configured, and validates against the chain's block gas limit from startup instead of a 30M default. No CLI flag changed (cli_snapshot passes unchanged).

Test Execution Summary

op-reth op-reth/v2.8.2 merged into streamingfast/optimism release/op-reth-2.x (branch bump/op-reth-2.8.2). Reth (streamingfast/reth op-reth-v2.8.1-fh3.1), alloy-evm (streamingfast/evm v0.39.0-sf) and firehose-tracer (5.5.0) are unchanged.

Build Status

  • cargo build --locked -p op-reth --bin op-reth (in rust/, dev profile, used for Battlefield): PASSED
  • cargo check --locked --workspace --all-targets (in rust/): PASSED
  • Docker image (rust/op-reth/Dockerfile.sf): NOT RUN locally; the sf-release.yml workflow builds it when the tag is pushed.

Unit Tests

Package / command Status Notes
cargo test --locked -p reth-optimism-firehose -p reth-optimism-node -p alloy-op-evm -p reth-optimism-payload-builder -p reth-optimism-evm -p op-alloy-consensus -p reth-optimism-cli -p op-reth -p reth-optimism-txpool --no-fail-fast PASSED alloy-op-evm 114, op-alloy-consensus 112 (+3 doc), reth-optimism-txpool 89, reth-optimism-evm 58, reth-optimism-node 51 + 26 (it) + 2 (e2e, 1 ignored) (+3 doc), reth-optimism-payload-builder 44 + 1, reth-optimism-cli 15, op-reth 5; reth-optimism-firehose has no unit tests
cargo test --locked -p reth-optimism-node --test it (rerun) PASSED 26 tests. In the first run custom_genesis::test_op_node_custom_genesis_number failed with "address 0.0.0.0:30303 is already in use": the Battlefield devnet's bootnode held that port. It passes once the devnet is down.
cargo test --locked -p reth-optimism-cli --all-features --test cli_snapshot PASSED 5 tests; snapshot unchanged
cargo test -p reth-firehose -p reth-firehose-tests (streamingfast/reth) NOT RUN Reth stays on the same commit as op-reth-v2.8.1-fh3.1, where these passed.

Integration Tests

  • Status: NOT RUN (no Firehose integration suite in the op-reth workspace beyond the tests above).

Battlefield Tests

  • Status: PASSED
  • Pass/Fail: 79 passing / 0 failing, 25 pending (fork-gated suites this network does not have: Amsterdam, BAL, EIP-7708, blob transactions, other chains' features)
  • Block comparison: the in-suite Compare blocks test ("Firehose blocks match RPC blocks") PASSED.
  • Setup: streamingfast/battlefield-ethereum master (ba78940), op-reth-devnet target, fireeth v2.24.1, builder-playground v0.3.3-sf1, local op-node v1.19.11:
    1. ./scripts/optimism/run_optimism_devnet.sh
    2. OP_RETH_BINARY=<optimism>/rust/target/debug/op-reth ./scripts/run_firehose_op_reth_devnet.sh
    3. pnpm test:fh3.0:op-reth-devnet
  • Fork coverage: the devnet activates every fork up to Jovian at genesis. Karst (active on OP Mainnet and Unichain) is not exercised, since builder-playground has no Karst support, and neither is Lagoon (not scheduled). The devnet's operator fee parameters are zero.

Firehose bug pattern review

  1. Serial order: none found. The range changes no block execution, prewarming or engine validator code.
  2. Emission after acceptance: none found. No new header field or post-execution check.
  3. Activations: no OpHardfork added, superchain-registry stays at 13907b9b and alloy-op-hardforks is unchanged, so no compiled-in timestamp moved. Lagoon is still unscheduled in the code, but Optimism's interop preparation notice now targets mid-December 2026 for OP Mainnet and Unichain (pending governance). Its 0x7D post-exec transaction is still unsupported by firehose-tracer 5.5.0 and the reth mapper (expect(...) in crates/firehose/src/mapper.rs), so the first such transaction would panic the node. ACTIVATIONS.md is refreshed.
  4. Fields and enums: OpTxEnvelope, OpTxType, OpReceipt, deposits and the header are unchanged; op-revm and the fee vault formulas are unchanged.
  5. Transactions without a hash: not affected by this release.

CHANGELOG

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

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

### Changed

* Merged upstream `op-reth/v2.8.2`, which keeps the interop transaction pool's `endpoint.up` gauge
  up when a filter answers `-321100` (out of scope) and shares the operator gas limit with the
  transaction pool. Block execution, the fork schedule and the reth and alloy-evm versions are
  unchanged.
* Reth and `alloy-evm` are pinned by commit instead of by tag, still on `streamingfast/reth`
  `op-reth-v2.8.1-fh3.1` and `streamingfast/evm` `v0.39.0-sf`.
* `ACTIVATIONS.md` records Optimism's mid-December 2026 target for Lagoon, which still has no
  timestamp in the code and still needs Firehose support for the `0x7D` post-exec transaction.

Not part of this PR

  • Lagoon support: a Firehose transaction type for 0x7D (firehose-tracer and the reth mapper) and a check of the gas passed to the fee vault credits under post-exec refunds. This must ship before Lagoon is scheduled on OP Mainnet or Unichain (see ACTIVATIONS.md).

sebastianst and others added 22 commits November 5, 2026 09:16
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
…y retry tests (ethereum-optimism#23972)

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

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

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

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

Co-authored-by: opsuperchain <opsuperchain@slop.bot>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Same commits as tags op-reth-v2.8.1-fh3.1 and v0.39.0-sf.
@sduchesneau
sduchesneau merged commit c137683 into release/op-reth-2.x Nov 10, 2026
2 checks passed
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.