Repository navigation
Conversation
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ethereum-optimism#23968) 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>
…m-optimism#23772) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…thereum-optimism#23775) Co-authored-by: Claude Opus 5.5 <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>
…thereum-optimism#24028) Co-authored-by: Claude Opus 5.5 <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>
ethereum-optimism#23780) Co-authored-by: Claude Opus 5.5 <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>
…ptimism#23786) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…nd upgrade (ethereum-optimism#23891) Co-authored-by: OneTony <onetony@defi.sucks>
…-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>
…es nightly (ethereum-optimism#24037) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ceipt race (ethereum-optimism#24041) Co-authored-by: Claude <noreply@anthropic.com>
…sm#24016) Co-authored-by: wwared <541936+wwared@users.noreply.github.com>
…-optimism#24057) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.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>
…-optimism#24003) 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>
…reum-optimism#24060) 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>
…optimism#24071) 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.
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.9.0(50 commits on top ofop-reth/v2.8.2) intorelease/op-reth-2.x. To be taggedop-reth-v2.9.0-fh3.1once merged (the tag the release tracker proposed, which follows the naming rule). The Firehose block model is unchanged, so the version staysfh3.1.Before merging
f965b380132b5a770e2a6cfaf3e8d9f68076f380, the commitrust/Cargo.tomlpins (it will be taggedop-reth-v2.9.0-fh3.1in streamingfast/reth).Merge order: streamingfast/reth#103 first, then this PR.
What changed
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.gascapnow capseth_estimateGas, three RPC limit flags reject0, error code4444for pruned history), lower RPC cache defaults and thesepolia-devnet-4/5/6chain configs.streamingfast/rethcommitf965b380(Merge op-v2.7.0-0 for op-reth v2.9.0 reth#103, future tagop-reth-v2.9.0-fh3.1), which mergesop-v2.7.0-0intorelease/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-tracermoves to 5.5.1.streamingfast/evmv0.39.0-sfpatch is unchanged.rust/Cargo.toml(upstream reindented it; rebuilt from upstream's file with our reth pins,firehose-tracer, the Firehose crate and thealloy-evmpatch),rust/Cargo.lock(upstream's lock re-resolved), andrust/op-reth/crates/trie/src/engine/tasks/execute_block.rs(keptexecute_oneso the proofs ExEx never prints a secondFIRE BLOCK, on top of upstream's newinto_evm_state_provider()).op-reth/crates/firehose/src/engine_validator.rs(our copy of reth's payload validator) and the built-block trace inop-reth/crates/payload/src/builder.rsnow read state through reth'sEvmStateProvider, like the upstream code they follow.release/op-reth-2.x(Stop proofs ExEx from printing Firehose blocks #31).Firehose review
extras.rsrecomputes the OP fee vault credits. In this range, op-revmhandler.rs,alloy-op-evmandreth-optimism-evmchange only comments and test plumbing, so the formulas are unchanged.debug_trace*/trace_*(and the new Lagoon SDM settlement replay) throughexecutor_for_block.OpFirehoseEvmConfigonly hooksbatch_executor, so RPC calls never print blocks.ACTIVATIONS.md): op-reth v2.9.0 defines no newOpHardfork. 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. TheACTIVATIONS.mdLagoon row now lists what Lagoon changes in the Firehose block (see Open questions).Dependencies
streamingfast/rethrelease/optimism-2.x(new PR Merge op-v2.7.0-0 for op-reth v2.9.0 reth#103) andstreamingfast/evmrelease/0.x(unchanged, no PR needed). The dependency table in the release tracker is correct.op-reth-v2.8.2-fh3.1).CHANGELOG
Open questions
Lagoon (not scheduled yet, targeted for January 11, 2027). With this release the node no longer panics on the
0x7Dpost-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:0x7Dtransaction without running the EVM, so its trace has no call. The tracer then drops its receipt and leaves its status unknown.OpPostTxExtrasruns 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.GasRefundleaves out the operator fee part of the refund when operator fees are nonzero. The same may already apply to the Isthmus operator fee refund fromreimburse_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
cargo check --workspace --all-targets: PASSEDrust/:cargo check --workspace --all-targets: PASSEDrust/:cargo build --release -p op-reth --bin op-reth: PASSEDUnit Tests
reth-firehosereth-firehose-tests(prestate golden files)reth-engine-tree --test firehose_live_tracingreth-optimism-firehoseop-alloy-consensus --features firehosereth-optimism-evmreth-optimism-payload-builderreth-optimism-trie(lib,tests/lib.rs,tests/live.rs)--test-threads=4(see notes)reth-optimism-node --test it builderNotes:
reth-optimism-triewith the default 60 test threads failed 88 tests with MDBXCannot allocate memory (12)when opening their test databases, all at once. With--test-threads=4all pass, so this is the test machine, not the merge.v0.3.3-sf1; the OP devnet needsv0.3.3-sf2(--sequencer-el,--enable-karst), built from source for this run.llvm-sys221 (LLVM 22). The build machine has LLVM 23 only; it builds withLLVM_SYS_221_PREFIX=/usr/lib/llvm-23and LLVM 23'sllvm-configfirst onPATH.Integration Tests
Battlefield Tests
Compare blocks(Firehose blocks against the node's JSON-RPC): PASSEDCommands (battlefield-ethereum
adb1921, builder-playgroundv0.3.3-sf2built from source, op-node v1.19.11, fireeth v2.24.1, op-reth fromcargo build --release -p op-reth --bin op-rethon 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