Updated on March 1, 2020

Static Nodes

Static nodes are a configured set of trusted nodes. Static nodes are exempt from maximum peer and remote connection limits.

Besu 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 bootnodes and statics nodes. For example, you run multiple nodes on MainNet (discovery using bootnodes), but want to ensure your nodes are always connected (using static nodes).

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

Configure static nodes

To configure a network of static nodes:

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

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

  3. Start Besu with discovery disabled using --discovery-enabled=false.

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


Runtime modifications of static nodes are not persisted 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 the 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 --data-path) 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.