Connect Public Nodes

What Are Public Nodes?

Public nodes are reachable Fiber nodes operated for Mainnet or Testnet connectivity. You can connect to them as peers so your node can join the public Fiber network, discover graph data, and prepare for channel operations.

Connecting to a public node only creates a peer connection. It does not open a channel or send payments by itself.

Public Node Information

Mainnet

Testnet

How to Connect

Use fnn-cli peer connect_peer with the public node pubkey:

fnn-cli peer connect_peer --pubkey <public_node_pubkey>

For example, to connect to Testnet node1:

fnn-cli peer connect_peer \
  --pubkey 02b6d4e3ab86a2ca2fad6fae0ecb2e1e559e0b911939872a90abdda6d20302be71

You can also call the connect_peer RPC directly:

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "connect_peer",
  "params": [
    {
      "pubkey": "<public_node_pubkey>"
    }
  ]
}

After connecting, check the peer list:

fnn-cli peer list_peers

Example response:

{
  "peers": [
    {
      "pubkey": "02b6d4e3ab86a2ca2fad6fae0ecb2e1e559e0b911939872a90abdda6d20302be71",
      "address": "/ip4/<public-node-ip>/tcp/<port>"
    }
  ]
}

If the node cannot resolve the pubkey yet, wait for graph data to sync or connect with a known multiaddr when one is available.

WebSocket Connections

Native Fiber nodes usually connect by pubkey after graph sync, or by a known TCP multiaddr.

WASM nodes running in a browser through the fiber-js package should use a public node WebSocket or WebSocket Secure multiaddr when one is available:

/dns/<host>/tcp/443/wss/p2p/<peer_id>

When connecting by pubkey, connect_peer can also filter resolved addresses with addr_type. Native builds default to tcp, while wasm builds default to ws and wss.

References

• connect_peer
• list_peers
• Network Resources