Skip to content

Commit 26bd41c

Browse files
authored
Merge pull request #52 from jpmorganchase/tylobban-bootnode-docs
document bootnode setup process
2 parents 95d4681 + b2c1398 commit 26bd41c

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

docs/running.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,9 +105,27 @@ From the above example, the `<256 bit aligned key value>` is the ethereum accoun
105105

106106
The `genesis.json` file can be found in the `7nodes` folder in the `quorum-examples` repository.
107107

108+
### Setup Bootnode
109+
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:
110+
111+
1- To generate the key for the first time:
112+
113+
`bootnode –genkey tmp_file.txt //this will start a bootnode with an enode address and generate a key inside a “tmp_file.txt” file`
114+
115+
2- To later restart the bootnode using the same key (and hence use the same enode url):
116+
117+
`bootnode –nodekey tmp_file.txt`
118+
119+
or
120+
121+
`bootnode –nodekeyhex 77bd02ffa26e3fb8f324bda24ae588066f1873d95680104de5bc2db9e7b2e510 // Key from tmp_file.txt`
122+
123+
108124
### Start node
109125

110-
Starting a node is as simple as `geth`. This will start the node without any of the roles and makes the node a spectator.
126+
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:
127+
128+
`geth --bootnodes $BOOTNODE_ENODE`
111129

112130
### Voting role
113131

0 commit comments

Comments
 (0)