Merge pull request #52 from jpmorganchase/tylobban-bootnode-docs

document bootnode setup process
This commit is contained in:
Samer Falah 2017-02-10 17:05:28 -05:00 committed by GitHub
commit 26bd41c292
1 changed files with 19 additions and 1 deletions

View File

@ -105,9 +105,27 @@ From the above example, the `<256 bit aligned key value>` is the ethereum accoun
The `genesis.json` file can be found in the `7nodes` folder in the `quorum-examples` repository.
### Setup Bootnode
Optionally you can set up a bootnode that all the other nodes will first connect to in order to find other peers in the network. You will first need to generate a bootnode key:
1- To generate the key for the first time:
`bootnode genkey tmp_file.txt //this will start a bootnode with an enode address and generate a key inside a “tmp_file.txt” file`
2- To later restart the bootnode using the same key (and hence use the same enode url):
`bootnode nodekey tmp_file.txt`
or
`bootnode nodekeyhex 77bd02ffa26e3fb8f324bda24ae588066f1873d95680104de5bc2db9e7b2e510 // Key from tmp_file.txt`
### Start node
Starting a node is as simple as `geth`. This will start the node without any of the roles and makes the node a spectator.
Starting a node is as simple as `geth`. This will start the node without any of the roles and makes the node a spectator. If you have setup a bootnode then be sure to add the `--bootnodes` param to your startup command:
`geth --bootnodes $BOOTNODE_ENODE`
### Voting role