Skip to content

Commit

Permalink
Merge pull request #52 from jpmorganchase/tylobban-bootnode-docs
Browse files Browse the repository at this point in the history
document bootnode setup process
  • Loading branch information
jpmsam authored Feb 10, 2017
2 parents 95d4681 + b2c1398 commit 26bd41c
Showing 1 changed file with 19 additions and 1 deletion.
20 changes: 19 additions & 1 deletion docs/running.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 26bd41c

Please sign in to comment.