op-stack EL: publish p2p port + discovery on for node_sync nodes (49 composes) #100

Merged
sebastian merged 1 commits from opstack-el-p2p-publish-discovery into main 2026-10-04 12:45:01 +00:00
Collaborator

Generated assets for vibe-node PR opstack-el-p2p-publish-discovery (operator decision sebastian 2026-10-04).

Every consensus-layer-synced op-stack EL (op-geth / op-reth / op-erigon, node_sync: true) now publishes client_port TCP+UDP, runs --nat=extip:${IP}, and keeps discovery ON (drops --nodiscover / --disable-discovery).

Why: blocks still arrive only via op-node + engine API. EL peers are used solely to backfill a dropped-gossip gap; with 0 peers that backfill never completes and op-node wedges in FCU-SYNCING until L1 derivation catches up (katana 09-19..26, zircuit, mode). Our own copies find each other implicitly, so the connect-peers mesh plan is superseded.

Rollout: canary rpc-de-25 (katana) → verify net_peerCount > 0 and katana dRPC ok-share → fleet.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RzxemENdcZBCxdGrzXiFvS

Generated assets for vibe-node PR `opstack-el-p2p-publish-discovery` (operator decision sebastian 2026-10-04). Every consensus-layer-synced op-stack EL (op-geth / op-reth / op-erigon, `node_sync: true`) now publishes `client_port` TCP+UDP, runs `--nat=extip:${IP}`, and keeps discovery ON (drops `--nodiscover` / `--disable-discovery`). Why: blocks still arrive only via op-node + engine API. EL peers are used solely to backfill a dropped-gossip gap; with 0 peers that backfill never completes and op-node wedges in FCU-SYNCING until L1 derivation catches up (katana 09-19..26, zircuit, mode). Our own copies find each other implicitly, so the connect-peers mesh plan is superseded. Rollout: canary rpc-de-25 (katana) → verify `net_peerCount` > 0 and katana dRPC ok-share → fleet. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01RzxemENdcZBCxdGrzXiFvS
claude added 1 commit 2026-10-04 11:55:43 +00:00
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
sebastian merged commit b493ef9988 into main 2026-10-04 12:45:01 +00:00
sebastian deleted branch opstack-el-p2p-publish-discovery 2026-10-04 12:45:01 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#100