[sameersubudhi]

What was the problem?

This PR resolves PLAT-850.

op-node and op-reth were pinned to v1.19.8 / v2.5.0. Upstream cut op-reth/v2.6.0, recommended for all operators, and op-node/v1.19.9, recommended for sequencers and optional for other nodes.

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

How was it solved?

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

None of op-reth's breaking changes require a change here. The entrypoint passes none of the removed --engine.sparse-trie-* flags. The isSystemTx format change only affects pre-Regolith deposits, which Lisk doesn't have. eth_getMultiProof was never served. The new engine persistence defaults do apply, since the image runs on defaults: 5 in-memory blocks, threshold 7. op-node drops the op_node_default_rpc_server_* metrics, which Lisk nodes export on port 7300; the release notes flag this for dashboard owners.

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 (6 checks against upstream)

Check	Result
Upstream tags, peeled	op-node/v1.19.9 and op-reth/v2.6.0 both resolve to da6d325
op-node-lisk-sepolia.patch	git apply --check passes; system_config.go byte-identical across v1.19.8/v1.19.9 (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); op-node/Makefile, rust/op-reth/bin/Cargo.toml and [profile.maxperf] unchanged; just build-superchain-go still present
superchain-registry submodule	Unchanged at 08d6a44
eth_getMultiProof in v2.5.0	Absent from crates/rpc of its reth pin (op-rs/reth@aef8d3e); v2.6.0 explicitly unserves it (rust/op-reth/crates/node/src/node.rs)

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

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated source-build instructions to use op-node v1.19.9 and op-reth v2.6.0, with the op-reth source link pointing to the v2.6.0 branch.
• Build Updates
  • Source builds now use the updated op-node and op-reth versions and verify both against the specified commit. The just installer is pinned to version 1.46.0.

[coderabbitai]

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: e570d8d4-19ca-4047-a89a-f8175de6be0d

📥 Commits

Reviewing files that changed from the base of the PR and between 436066d and 5a9b98f.

📒 Files selected for processing (1)

• 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 Docker build now pins just 1.46.0, op-node v1.19.9, and op-reth v2.6.0. The README source-build instructions and source-tree link use the updated OP Stack versions.

Changes

OP Stack Version Update

Layer / File(s)	Summary
Update build pins reth/Dockerfile	The Docker build pins just to 1.46.0 and checks out updated op-node and op-reth commits.
Align source-build documentation README.md	The README references op-node v1.19.9, op-reth v2.6.0, and the v2.6.0 source-tree branch.

Priority: ⬇️ Low

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

Change: Other

Possibly related PRs

• LiskHQ/lisk-node#131: Updates the same op-node and op-reth source pins and README build versions.

Merge Risk: ⚪ Minimal · up to 5a9b9

The upgrade removes some OP Node RPC metric series, so dashboards that depend on them would lose those measurements. No such consumer or other concrete regression is established in the supplied evidence; the PR is mergeable after normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the primary change: bumping op-node to v1.19.9 and op-reth to v2.6.0.
Description check	✅ Passed	The description includes all template sections. It identifies the problem and issue, explains the implementation, and describes testing and its limits.
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.

✨ 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

---

_{A rabbit hops past pinned tools,
just stands neat at one-four-six-oh.
OP nodes climb to newer roots,
While README paths in sync now grow.
Fresh commits guide the build below.}

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