[sameersubudhi]

What was the problem?

This PR resolves PLAT-847.

op-node and op-reth were pinned to v1.19.7 / v2.4.4. Upstream cut op-reth/v2.5.0, recommended for all operators for its rustls and imbl security updates, and op-node/v1.19.8, recommended for sequencers.

No env, peer, entrypoint or flag change is needed.

How was it solved?

• reth/Dockerfile: op-node VERSION → v1.19.8, op-reth VERSION → op-reth/v2.5.0, both COMMIT → 9f76a9d (the peeled commit both tags point to).
• README.md: client versions and the op-reth source-tree link.

Neither upstream breaking change affects this image. op-reth drops import-op / import-receipts-op, which import pre-Bedrock OVM history; Lisk has none and nothing here calls them. op-node now rejects rollup configs that activate Jovian or a later fork at the same post-genesis timestamp as its predecessor. Lisk Mainnet and Sepolia load from the embedded registry via --network, and both schedules comply.

How was it tested?

CI builds the image on linux/amd64 and linux/arm64, which runs both clone-and-verify steps and both compilations. I did not build locally.

Evidence (7 checks against upstream)

Check	Result
Dockerfile clone-and-verify, replayed for both tags	Both resolve to 9f76a9d
op-node-lisk-sepolia.patch	Applies; system_config.go byte-identical across v1.19.7/v1.19.8 (blob 7b368b2)
dockerfile-lisk-sepolia.patch	git apply --check passes against the new Dockerfile
GOLANG_VERSION=1.26 / RUST_VERSION=1.95	Match upstream go.mod (go 1.26.0) and rust/rust-toolchain.toml (1.95)
superchain-registry submodule	Unchanged at 08d6a44
Fork-order check vs Lisk schedules (registry 08d6a44)	Mainnet and Sepolia: Jovian and Karst each activate strictly after their predecessor
op-node diffs absent from upstream notes	Span-batch post-exec checks need Lagoon, which Lisk hasn't scheduled. The EL-sync safe-head change reduces to the local safe head on Lisk's verifier config. L1 receipts prefetch only runs on sequencers

Release draft v0.4.30 is prepared against main and will be published after this merges.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Source-build guidance now reflects op-node v1.19.8 and op-reth v2.5.0, including the updated op-reth source branch.
• Build Updates
  • Build configurations now use these updated versions, with checkout verification retained for both components. This keeps documented build instructions aligned with the versions used to produce builds.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 54c01dd8-44f8-4f3a-9a41-bb31360775a6

📥 Commits

Reviewing files that changed from the base of the PR and between a3a6e30 and 37dd9c4.

📒 Files selected for processing (2)

• README.md
• reth/Dockerfile

Included review availability: This review used your included allowance. 3 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

---

📝 Walkthrough

Walkthrough

The Dockerfile source checkouts and README references change to op-node v1.19.8 and op-reth v2.5.0. The Dockerfile pins both checkouts to commit 9f76a9d216f2d9aa99c5f45d7aad674acde93c14.

Changes

Source Version Update

Layer / File(s)	Summary
Update source versions reth/Dockerfile, README.md	The Dockerfile uses the updated op-node and op-reth tags and commit pins. The README lists the updated versions and links to the op-reth v2.5.0 source tree.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~4 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 37dd9

The version update has no identified compatibility blocker: both Lisk schedules pass the updated fork-order validation, and the image workflows do not rely on the removed commands.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the two version bumps and includes the related issue identifier.
Description check	✅ Passed	The description includes all required sections. It explains the problem, implementation, and testing, with detailed evidence and relevant compatibility notes.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

_{A rabbit checks the version tags,
Then hops along the source-tree tracks.
Two pins now point to commits new,
The README lists the versions too.
A quiet nibble marks the change.}

_{Comment @coderabbitai help to get the list of available commands.}