Summary
The published Ink mainnet op-node P2P bootstrap endpoints in envs/ink-mainnet/op-node.env appear to be down. Nodes that rely on them cannot join the gossip mesh and therefore cannot follow the unsafe tip when using --syncmode=execution-layer.
Published config (current main)
OP_NODE_P2P_BOOTNODES="enr:-Iu4QCqTQZVBnbPWXcdUxcakGoCCzCFr5vVzDfNTOr-Pi3KaOJZMXlnqTR9r9p4EemXS8fS59EdQaX8qrkyE01nvsNcBgmlkgnY0gmlwhCIgwYaJc2VjcDI1NmsxoQMW3w0F1AibYelKqJUKaie5RuKc7S9sPfWvH4lSJw4Fo4N0Y3CCIyuDdWRwgiMs"
OP_NODE_P2P_STATIC="/ip4/34.32.193.134/tcp/9003/p2p/16Uiu2HAmECGb1vmBKhgxVHzX2aYkPcmV8CZjpPxrNkRiFA1wa3CN"
The bootnode ENR resolves to the same host (34.32.193.134) as OP_NODE_P2P_STATIC.
Evidence (checked 2026-08-04)
From multiple networks:
| Check |
Result |
ICMP to 34.32.193.134 |
Host responds (ping OK) |
TCP 34.32.193.134:9003 |
connection refused |
| TCP 9222 / 30303 / 8545 on same host |
also refused |
op-node log |
repeated error dialing static peer … dial tcp4 34.32.193.134:9003: connect: connection refused |
Local op_node_default_p2p_peer_count |
stays 0 |
| Local unsafe payloads |
0 |
Example op-node warning:
msg="error dialing static peer" peer=16Uiu2HAmECGb1vmBKhgxVHzX2aYkPcmV8CZjpPxrNkRiFA1wa3CN
err="failed to dial ... dial tcp4 34.32.193.134:9003: connect: connection refused"
These values have been unchanged in git history since the initial mainnet env was added (Dec 2024).
Our own node listens correctly on TCP/UDP 9003 and is reachable from the public internet; the failure is specifically outbound to the published Ink bootstrap peer.
Impact
- Fresh starts / restarts cannot bootstrap P2P discovery.
- With
OP_NODE_SYNCMODE=execution-layer, the node stops receiving unsafe payloads and falls behind the public unsafe tip.
- Falling back to
consensus-layer still works for L1-derived safe head, but lags public RPCs that follow unsafe head.
Related: #84 (request for trusted peers; no reply yet).
Request
Please either:
- Restore the mainnet static/bootnode service on
34.32.193.134:9003, or
- Publish updated
OP_NODE_P2P_BOOTNODES / OP_NODE_P2P_STATIC values for ink-mainnet in envs/ink-mainnet/op-node.env.
Happy to re-test connectivity as soon as new endpoints are published.
Summary
The published Ink mainnet op-node P2P bootstrap endpoints in
envs/ink-mainnet/op-node.envappear to be down. Nodes that rely on them cannot join the gossip mesh and therefore cannot follow the unsafe tip when using--syncmode=execution-layer.Published config (current
main)The bootnode ENR resolves to the same host (
34.32.193.134) asOP_NODE_P2P_STATIC.Evidence (checked 2026-08-04)
From multiple networks:
34.32.193.13434.32.193.134:9003connection refusedop-nodelogerror dialing static peer…dial tcp4 34.32.193.134:9003: connect: connection refusedop_node_default_p2p_peer_count00Example
op-nodewarning:These values have been unchanged in git history since the initial mainnet env was added (Dec 2024).
Our own node listens correctly on TCP/UDP
9003and is reachable from the public internet; the failure is specifically outbound to the published Ink bootstrap peer.Impact
OP_NODE_SYNCMODE=execution-layer, the node stops receiving unsafe payloads and falls behind the public unsafe tip.consensus-layerstill works for L1-derived safe head, but lags public RPCs that follow unsafe head.Related: #84 (request for trusted peers; no reply yet).
Request
Please either:
34.32.193.134:9003, orOP_NODE_P2P_BOOTNODES/OP_NODE_P2P_STATICvalues for ink-mainnet inenvs/ink-mainnet/op-node.env.Happy to re-test connectivity as soon as new endpoints are published.