fix: refresh op-node P2P bootstrap and static peers - #86
Merged
Conversation
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
The configured mainnet and sepolia P2P endpoints point at hosts that no longer accept connections. Each network had a single static peer, and on mainnet the bootnode ENR and the static peer resolved to the same address, so there was no fallback once it stopped answering. Nodes using these values cannot join the gossip mesh and never receive unsafe payloads. They still derive the safe chain from L1, so they appear to sync while permanently trailing the network by the batch posting interval. Replace both with the current published endpoints: 6 bootnodes and 3 static peers on mainnet, 5 and 3 on sepolia. All six static peers were verified reachable on TCP 9003. Also record the execution-layer peers for the planned op-reth migration, and correct the static-peer troubleshooting entry, which advised that an advancing current_l1 meant the node was still making progress. That value is unaffected by peer count, so it cannot distinguish a healthy node from one with no peers at all; point at opp2p_peerStats instead. Fixes #85
lucass555
force-pushed
the
fix/refresh-p2p-peer-endpoints
branch
from
August 5, 2026 15:27
b8985b5 to
30ab400
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The configured mainnet and sepolia P2P endpoints point at hosts that no longer accept connections. Each network had a single static peer, and on mainnet the bootnode ENR and the static peer resolved to the same address, so there was no fallback once it stopped answering.
Nodes using these values cannot join the gossip mesh and never receive unsafe payloads. They still derive the safe chain from L1, so they appear to sync while permanently trailing the network by the batch posting interval.
Replace both with the current published endpoints: 6 bootnodes and 3 static peers on mainnet, 5 and 3 on sepolia. All six static peers were verified reachable on TCP 9003.
Fixes #85