Skip to content

Commit

Permalink
Merge branch 'main' into 1458ReplacTxns
Browse files Browse the repository at this point in the history
  • Loading branch information
alexandratran authored Dec 1, 2023
2 parents 9202748 + aa9b5d7 commit fd5e784
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 3 deletions.
8 changes: 6 additions & 2 deletions docs/public-networks/how-to/connect/static-nodes.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,15 @@ tags:

Static nodes are a configured set of trusted nodes. Static nodes are exempt from [maximum peer](manage-peers.md#limit-peers) and [remote connection](manage-peers.md#limit-remote-connections) limits.

Besu attempts to maintain connections with static nodes by periodically initiating a connection to any unconnected static node.
Besu periodically initiates a connection to any unconnected static node. To mitigate low peer count issues in small networks, we recommend using static nodes, or static nodes and bootnodes.

:::tip

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 static nodes. For example, you run multiple nodes on Mainnet (discovery using bootnodes), but want to ensure your nodes are always connected (using static nodes).
Bootnodes and static nodes are both methods for finding peers. Depending on your use case, you can use only bootnodes, only static nodes, or both bootnodes and static nodes.

For example:
* You run multiple nodes on Mainnet, using bootnodes for discovery, but want to ensure your nodes are always connected to each other, using static nodes.
* You run a small network and want your nodes to reconnect if disconnected, using static nodes.

To find peers, configure one or more [bootnodes](../../../private-networks/how-to/configure/bootnodes.md). To configure a specific set of peer connections, use static nodes.

Expand Down
2 changes: 1 addition & 1 deletion docs/public-networks/how-to/use-besu-api/authenticate.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ The private key must be kept secret. Never share private keys publicly or on a W

Always keep your private keys safe -- ideally using [hardware](https://connect2id.com/products/nimbus-jose-jwt/examples/pkcs11) or [vault](https://www.vaultproject.io/docs/secrets/identity/identity-token) -- and define a strong security policy and [best practices](https://auth0.com/docs/best-practices/token-best-practices).

Compromised keys can provide attackers access to you nodes RPC-API.
Compromised keys can provide attackers access to your node's RPC-API.
:::
Expand Down

0 comments on commit fd5e784

Please sign in to comment.