Skip to main content

Configure static nodes

Static nodes are a configured set of trusted nodes. They're exempt from maximum peer limits set through the --maxpeers option.

GoQuorum attempts to maintain connections with static nodes by periodically initiating a connection to any unconnected static node.


Bootnodes and static nodes are parallel methods for finding peers. Depending on your use case, you can use only bootnodes, only static nodes, or both.

To find peers, configure one or more bootnodes. To configure a specific set of peer connections, use static nodes, as described on this page.

Configure static nodes

To configure a network of static nodes:

  1. List the enode URLs of the nodes in the static-nodes.json file.


    When specifying enodes in static-nodes.json, you can use either DNS names or IP addresses. Only bootnodes need to be specified with IP addresses.

  2. Save the static-nodes.json file in the data directory (specified by --datadir) of each node.

  3. Start GoQuorum with discovery disabled using --nodiscover.

To update the list of static peers at runtime, use the admin_addPeer and admin_removePeer JSON-RPC API methods.


Runtime modifications of static nodes do not persist between runs. The static-nodes.json file is not updated by the admin_addPeer and admin_removePeer methods.

Nodes not in the list of the static nodes are not prevented from connecting. To prevent nodes from connecting, use permissioning.


If the added peer does not appear in the peer list (returned by admin_peers), check that the supplied enode URL is correct, the node is running, and the node is listening for TCP connections on the endpoint.

static-nodes.json file

The static-nodes.json file must be in the data directory (specified by --datadir) and contain a JSON array of enode URLs.


Each node has a static-nodes.json file. We recommend each node in the network has the same static-nodes.json file.