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

     1  # Basics
     2  
     3  You can spin up a single node chain with:
     4  
     5  ```shell
     6  burrow spec -v1 | burrow configure -s- | burrow start -c-
     7  ```
     8  
     9  ## Configuration
    10  
    11  The quick-and-dirty one-liner looks like:
    12  
    13  ```shell
    14  # Read spec on stdin
    15  burrow spec -p1 -f1 | burrow configure -s- > burrow.toml
    16  ```
    17  
    18  Which translates into:
    19  
    20  ```shell
    21  burrow spec --participant-accounts=1 --full-accounts=1 > genesis-spec.json
    22  burrow configure --genesis-spec=genesis-spec.json > burrow.toml
    23  ```
    24  
    25  > You might want to run this in a clean directory to avoid overwriting any previous spec or config.
    26  
    27  ## Running
    28  
    29  Once the `burrow.toml` has been created, we run:
    30  
    31  ```
    32  # To select our validator address by index in the GenesisDoc
    33  burrow start --validator=0
    34  # Or to select based on address directly (substituting the example address below with your validator's):
    35  burrow start --address=BE584820DC904A55449D7EB0C97607B40224B96E
    36  ```
    37  
    38  If you would like to reset your node, you can just delete its working directory with `rm -rf .burrow`. 
    39  In the context of a multi-node chain it will resync with peers, otherwise it will restart from height 0.
    40  
    41  ## Keys
    42  
    43  Burrow consumes its keys through our key signing interface that can be run as a standalone service with:
    44  
    45  ```shell
    46  burrow keys server
    47  ```
    48  
    49  This command starts a key signing daemon capable of generating new ed25519 and secp256k1 keys, naming those keys, signing arbitrary messages, and verifying signed messages.
    50  It also initializes a key store directory in `.keys` (by default) where private key matter is stored.
    51  
    52  It should be noted that the GRPC service exposed by the keys server will sign _any_ inbound requests using the keys it maintains so the machine running the keys service should only allow connections from sources that are trusted to use those keys.