Besu attempts to maintain connections with static nodes by periodically initiating a connection to any static node that is not connected.
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 via bootnode) 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:
static-nodes.jsonfile in the data directory of each node.
Start Besu with discovery disabled using
Runtime modifications of static nodes are not persisted between runs. The
is not updated by
Nodes outside 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
check the supplied enode URL is correct, the node is running, and the node is listening for
TCP connections on the endpoint.
Each node has a
static-nodes.json file. We recommend each node in the network has the same