From 1e35387c04f5ff7d97a08188c767b4ea0680c469 Mon Sep 17 00:00:00 2001 From: Roman Khimov Date: Fri, 13 Jan 2023 11:33:19 +0300 Subject: [PATCH] docs: fix the MinPeers consensus requirements It won't work with 1 for a single node and 3 for 4 CN scenario doesn't allow the network to start with just three nodes (although technically 3 out of 4 is sufficient to operate). See #2874. --- docs/consensus.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/consensus.md b/docs/consensus.md index 3c9e6322f..2a3e300be 100644 --- a/docs/consensus.md +++ b/docs/consensus.md @@ -189,10 +189,11 @@ Examples can be found at `config/protocol.privnet.docker.one.yml` (`two`, `three `UnlockWallet` subsection with `Path` and `Password` strings for NEP-6 wallet path and the password for the account to be used for the consensus node. - 2. Make sure that your `MinPeers` setting is equal to - the number of nodes participating in consensus. - This requirement is needed for nodes to correctly - start and can be weakened in future. + 2. Make sure that your `MinPeers` setting is no more than + the number of nodes participating in consensus minus one. The + recommended setting is 2F in terms of BFT, that's the minimum number + the network can operate with (0 for a single node, 2 for 4 CNs, 4 for 7 + CNs). 3. Set `Address`, `Port` and `RPC.Port` to the appropriate values. They must differ between nodes. 4. If you start binary from the same directory, you will probably want to change