github.com/hyperledger/burrow@v0.34.5-0.20220512172541-77f09336001d/docs/tutorials/4-networking.md (about)

     1  # Networking
     2  
     3  So far we have only run a single validator. What happens if it stops working or loses its data?
     4  We're much better off running multiple nodes in parallel!
     5  
     6  ## Getting Started
     7  
     8  Let's configure a local chain with two full accounts:
     9  
    10  ```shell
    11  burrow spec -f2 | burrow configure -s- --pool
    12  ```
    13  
    14  You'll notice that Burrow has generated two config files instead of one, hold on to these.
    15  
    16  
    17  ## First Node
    18  
    19  ```shell
    20  burrow start --config=burrow000.toml
    21  ```
    22  
    23  You will see `blockpool has no peers` in the logs, this means that the node has not got enough validator power in order to have 
    24  quorum (2/3) on the network, so it is blocked waiting for the second validator to join.
    25  
    26  ## Second Node
    27  
    28  ```shell
    29  burrow start --config=burrow001.toml
    30  ```
    31  
    32  If the connection succeeds, you will see empty blocks automatically created.
    33  Look for logs such as `Sending vote message` or `Finalizing commit of block with 0 txs`.
    34  
    35  You can also query the consensus state over our RPC with:
    36  
    37  ```shell
    38  curl -s 127.0.0.1:26758/consensus
    39  ```