From ad51b4e89c4fde464702c3fe07a9841d153f52c5 Mon Sep 17 00:00:00 2001 From: Gabriel-Trintinalia Date: Mon, 8 Jan 2024 13:26:47 +1100 Subject: [PATCH] Update versioned_docs/version-23.10.3/private-networks/how-to/configure/bootnodes.md Co-authored-by: Sally MacFarlane Signed-off-by: Gabriel-Trintinalia --- .../private-networks/how-to/configure/bootnodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-23.10.3/private-networks/how-to/configure/bootnodes.md b/versioned_docs/version-23.10.3/private-networks/how-to/configure/bootnodes.md index 72c0d24eae6..53a2b05d083 100644 --- a/versioned_docs/version-23.10.3/private-networks/how-to/configure/bootnodes.md +++ b/versioned_docs/version-23.10.3/private-networks/how-to/configure/bootnodes.md @@ -42,7 +42,7 @@ By default, peer discovery listens on all available network interfaces. If the d ## Configure bootnodes in a production network -A network must have at least one operating bootnode. To allow for continuity in the event of failure, configure two or more bootnodes in a production network. In case of no bootnodes, Mainnet default bootnodes will be used. +A network must have at least one operating bootnode. To allow for continuity in the event of failure, configure two or more bootnodes in a production network. If you don't configure any bootnodes, Mainnet default bootnodes will be used. We don't recommend putting bootnodes behind a load balancer because the [enode](../../../public-networks/concepts/node-keys.md#enode-url) relates to the node public key, IP address, and discovery ports. Any changes to a bootnode enode prevents other nodes from being able to establish a connection with the bootnode. This is why we recommend putting more bootnodes on the network itself.