[sameersubudhi]

What was the problem?

This PR resolves PLAT-969.

Upstream released op-node/v1.20.1 (optional) and op-reth/v2.8.1 (recommended for all operators). The op-reth tag also moves reth to fork tag op-v2.6.0-2, which backports a trie iterator fix (paradigmxyz/reth#28264) that upstream's release notes don't mention.

None of the remaining upstream changes affect Lisk. The eth_capabilities fix applies only to chains with pre-Bedrock history, and Lisk is Bedrock at genesis. This image uses neither of op-node's removals, --sequencer.max-safe-lag and the built-in Holesky L1 config. No env, peer, entrypoint or flag change is needed.

How was it solved?

• reth/Dockerfile: op-node pinned to v1.20.1 (f73158e) and op-reth to op-reth/v2.8.1 (7220729). RUST_VERSION 1.95 → 1.99 to match upstream's rust/rust-toolchain.toml. Go 1.26.10, just 1.46.0 and Ubuntu 26.04 are unchanged upstream.
• README.md: client versions and the op-reth source-tree link.

How was it tested?

I built the image natively on arm64 with PROFILE=release and FEATURES=jemalloc. CI covers the maxperf build on both linux/amd64 and linux/arm64. The first amd64 run failed on a transient GitHub 504 while downloading the just 1.46.0 release asset, before the clone step; the rerun is the verdict.

Evidence (9 checks)

Check	Result
Upstream tags, peeled	op-node/v1.20.1 → f73158e, op-reth/v2.8.1 → 7220729: different commits this time
Toolchains	go.mod toolchain go1.26.10 and mise.toml just 1.46.0 at both tags. rust/rust-toolchain.toml 1.95 → 1.99; rust:1.99 is Debian trixie, like rust:1.95
reth base	rust/Cargo.toml: tag op-v2.6.0-1 → op-v2.6.0-2, 3 commits on ethereum-optimism/reth; the only code change is the paradigmxyz/reth#28264 backport (crates/trie/trie/src/node_iter.rs). Base stays v2.6.0
superchain-registry	13907b9 at both tags, unchanged
Build recipes	op-node/Makefile unchanged. build-superchain-go still exists; only its script moves to op-core/superchain/bundle/. rust/op-reth/bin/Cargo.toml still defines jemalloc and asm-keccak; rust/Cargo.toml still has profile.maxperf
Flags removed upstream	reth-entrypoint, op-node-entrypoint and .env.mainnet set none of --sequencer.max-safe-lag, OP_NODE_SEQUENCER_MAX_SAFE_LAG or --rollup.l1-chain-config. Lisk's L1 is Ethereum Mainnet
eth_capabilities	op-reth clamps only when the Bedrock block is > 0; lisk.toml has genesis.l2.number = 0
op-node binary	v1.20.1-f73158e5
op-reth on Ubuntu 26.04	glibc 2.43; ldd resolves all libraries; dump-genesis --chain lisk returns chain ID 1135. --version reports 0.0.0-dev, as on v2.8.0

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

🤖 Generated with Claude Code

Summary by CodeRabbit

• Updates
  • Updated documented and container-build versions of op-node and op-reth.
  • Updated the Rust version used for container builds.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The Dockerfile now uses Rust 1.99 and pins op-node to v1.20.1 and op-reth to v2.8.1 with updated commit hashes. The README documents the new op-node and op-reth versions and links to the v2.8.1 op-reth source tree.

Changes: Build version updates

Layer / File(s)	Summary
Build inputs and version documentation reth/Dockerfile, README.md	The Dockerfile updates the Rust build-stage version and the op-node and op-reth version pins and commit hashes. The README documents the new op-node and op-reth versions and updates the op-reth source-tree link.

Estimated code review effort: 2 (Simple) | ~8 minutes

Possibly related PRs

• LiskHQ/lisk-node#150: Updates the same Dockerfile pins and README versions to the preceding op-node and op-reth releases.
• LiskHQ/lisk-node#146: Updates earlier op-node and op-reth pins and their README documentation.
• LiskHQ/lisk-node#144: Advances the same pins and documented versions in an earlier update.

Suggested reviewers: nazgolze

Merge Risk: Minimal · up to ed607

No merge-blocking risk is identified in the supplied changes.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly summarizes the upgrade of op-node and op-reth to the specified versions.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description check		The description follows the repository template. It has the sections "What was the problem?", "How was it solved?", and "How was it tested?". It links the issue PLAT-969 and states the reason for the …

Full details: Description check

Explanation

The description follows the repository template. It has the sections "What was the problem?", "How was it solved?", and "How was it tested?". It links the issue PLAT-969 and states the reason for the bump: upstream op-node v1.20.1 and op-reth v2.8.1 releases, plus the reth fork tag change to op-v2.6.0-2. It lists the file-level changes for reth/Dockerfile and README.md, including the RUST_VERSION change from 1.95 to 1.99. It explains why the removed upstream flags and the eth_capabilities fix do not affect Lisk. The testing section reports a native arm64 release build with jemalloc, the CI plan, and a supporting table of verification checks. The template placeholder #INSERT_ISSUE_NUMBER was replaced with a real Linear issue reference. The description is thorough and specific. Minor gap: it refers to the issue by Linear ID only, not a GitHub issue number, which is acceptable for this repository's usage.

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

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

_{A rabbit checks the build recipe with care,
New version numbers hop into the air.
The source link follows where the branches go,
Rust gets a fresh number in the row.
Then carrots crunch; the changes are complete.}

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: 91233052-0307-48f9-8371-249ee7963067

Commits

Reviewing files that changed from the base of the PR and between dab76b5 and ed607fd.

Files selected for processing: 2

• README.md
• reth/Dockerfile

Included review availability: This review used your included allowance. 4 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.