Repository navigation
Merge op-reth v2.8.2 - #30
Merged
Merged
Conversation
…m-optimism#23907) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…optimism#23914) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…eum-optimism#23949) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
…timism#23955) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
ethereum-optimism#23948) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ereum-optimism#23951) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.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>
ethereum-optimism#23958) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…-optimism#23985) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…timism#23981) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…reum-optimism#23994) Co-authored-by: Akosh Farkash <aakoshh@gmail.com>
Same commits as tags op-reth-v2.8.1-fh3.1 and v0.39.0-sf.
sduchesneau
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merges upstream
op-reth/v2.8.2(18 commits on top ofop-reth/v2.8.1) intorelease/op-reth-2.x. Release tag once merged:op-reth-v2.8.2-fh3.1(newest tag on the branch isop-reth-v2.8.1-fh3.1; the Firehose block model is unchanged, sofh3.1stays).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
endpoint.upgauge stays up when a filter answers-321100(out of scope); the operator gas limit (OpGasLimitConfig, now inreth-optimism-txpool) is shared with the transaction pool, which starts with the chain's block gas limit; new pool admission tests; kona rollup config gainssettlement_chain_id(not in the op-reth binary). The merge had no conflicts.alloy-evmare now pinned by commit with the tag in a comment, on the same releases as before:streamingfast/reth93fb772a…(op-reth-v2.8.1-fh3.1) andstreamingfast/evm52afebec…(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.gh search codeconfirms apart from the deployment configuration.Operator-visible changes from upstream
cli_snapshotpasses unchanged).Test Execution Summary
op-reth
op-reth/v2.8.2merged intostreamingfast/optimismrelease/op-reth-2.x(branchbump/op-reth-2.8.2). Reth (streamingfast/rethop-reth-v2.8.1-fh3.1),alloy-evm(streamingfast/evmv0.39.0-sf) andfirehose-tracer(5.5.0) are unchanged.Build Status
cargo build --locked -p op-reth --bin op-reth(inrust/, dev profile, used for Battlefield): PASSEDcargo check --locked --workspace --all-targets(inrust/): PASSEDrust/op-reth/Dockerfile.sf): NOT RUN locally; thesf-release.ymlworkflow builds it when the tag is pushed.Unit Tests
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-fastcargo test --locked -p reth-optimism-node --test it(rerun)custom_genesis::test_op_node_custom_genesis_numberfailed 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_snapshotcargo test -p reth-firehose -p reth-firehose-tests(streamingfast/reth)op-reth-v2.8.1-fh3.1, where these passed.Integration Tests
Battlefield Tests
Compare blockstest ("Firehose blocks match RPC blocks") PASSED.master(ba78940),op-reth-devnettarget, fireeth v2.24.1, builder-playground v0.3.3-sf1, local op-node v1.19.11:./scripts/optimism/run_optimism_devnet.shOP_RETH_BINARY=<optimism>/rust/target/debug/op-reth ./scripts/run_firehose_op_reth_devnet.shpnpm test:fh3.0:op-reth-devnetFirehose bug pattern review
OpHardforkadded,superchain-registrystays at13907b9bandalloy-op-hardforksis 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). Its0x7Dpost-exec transaction is still unsupported byfirehose-tracer5.5.0 and the reth mapper (expect(...)incrates/firehose/src/mapper.rs), so the first such transaction would panic the node.ACTIVATIONS.mdis refreshed.OpTxEnvelope,OpTxType,OpReceipt, deposits and the header are unchanged;op-revmand the fee vault formulas are unchanged.CHANGELOG
Not part of this PR
0x7D(firehose-tracerand 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 (seeACTIVATIONS.md).