You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/running.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,9 +105,27 @@ From the above example, the `<256 bit aligned key value>` is the ethereum accoun
105
105
106
106
The `genesis.json` file can be found in the `7nodes` folder in the `quorum-examples` repository.
107
107
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
+
108
124
### Start node
109
125
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:
0 commit comments