TrueCloudLab/neo-go
8
0
Fork 0
mirror of https://github.com/nspcc-dev/neo-go.git synced 2024-11-22 09:29:38 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs: fix the MinPeers consensus requirements

Browse source 
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.
This commit is contained in:
Roman Khimov 2023-01-13 11:33:19 +03:00
parent efbef4254a
commit 1e35387c04
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docs/consensus.md
View file

@ -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 `UnlockWallet` subsection with `Path` and `Password` strings for NEP-6
wallet path and the password for the account to be used for the wallet path and the password for the account to be used for the
consensus node. consensus node.
2. Make sure that your `MinPeers` setting is equal to 2. Make sure that your `MinPeers` setting is no more than
the number of nodes participating in consensus. the number of nodes participating in consensus minus one. The
This requirement is needed for nodes to correctly recommended setting is 2F in terms of BFT, that's the minimum number
start and can be weakened in future. 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. 3. Set `Address`, `Port` and `RPC.Port` to the appropriate values.
They must differ between nodes. They must differ between nodes.
4. If you start binary from the same directory, you will probably want to change 4. If you start binary from the same directory, you will probably want to change