katana-mainnet (2 composes): enode @35.197.34.76:30303 from katana-network/network-configs.
hashkeychain mainnet + xlayer testnet: their existing client_staticpeers were silently dropped
by op-reth.yml until now; they take effect with this change.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RzxemENdcZBCxdGrzXiFvS
Operator decision 2026-10-04 (sebastian): consensus-layer-synced op-stack nodes used to run
with --nodiscover / --disable-discovery and no published p2p port. A 0-peer EL can never
backfill a dropped-gossip gap, so op-node wedges in FCU-SYNCING until L1 derivation
catches up (katana 09-19..26, zircuit, mode). Blocks still arrive only via op-node; EL
peers are for gap-fill. Our own copies now discover each other implicitly.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RzxemENdcZBCxdGrzXiFvS
PR #5204 incorrectly bumped op.clients.reth.client_version (op-reth image)
from v2.4.3 to v2.5.2. The us-docker.pkg.dev/oplabs-tools-artifacts/images/op-reth
registry has no v2.5.2 tag, causing deploy failures on chains like bob.sepolia
and soneium.mainnet that inherit the default op-reth client without override.
This reverts only the op-reth version change, keeping the intended top-level
reth (ghcr.io/paradigmxyz/reth) bump to v2.5.2 intact.
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
The false default forced every op-node restart to walk back to the finalized head
before driving the EL. On nodes whose derivation lags days behind their serving
gossip head (hashkey us-40: 510k blocks / 12 days), that froze the EL for hours
while dRPC de-routed the sole US provider. true resumes at the unsafe head in
minutes; safe/finalized still verify and catch up in the background. ronin
already ran true per-chain (same lesson); xlayer keeps its deliberate false pin.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Also regenerate compose for already-merged hashkey static-peers / op-geth
static-nodes entrypoint (parent #1437) that had not yet landed in rpc.
Co-authored-by: Cursor <cursoragent@cursor.com>
Persist OP_NODE_SYNCMODE=consensus-layer and OP_NODE_L2_SKIP_SYNC_START_CHECK=true
so op-node drives the EL via engine API (no EL P2P peers on katana mainnet).
Co-authored-by: Cursor <cursoragent@cursor.com>
claudeandClaude Fable 5.1
robandClaude Opus 4.8