From 847c7818ddcae43d7092cc3931e46231bf8a9841 Mon Sep 17 00:00:00 2001 From: Tyrone Lobban Date: Fri, 10 Feb 2017 15:53:43 +0000 Subject: [PATCH 1/5] Update running.md --- docs/running.md | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/docs/running.md b/docs/running.md index 9621c639294a..71c2c2bc7bf7 100644 --- a/docs/running.md +++ b/docs/running.md @@ -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 you can use when starting up a Node in order that new peers will be auto-added to the network. You will need to generate a bootnode key and enode: + +1- To generate the key for the first time: + +`bootnode –genkey tmp_file.txt //this will generate a key inside a “tmp_file.txt” file` + +2- To start using the key and start your bootnode: + +`bootnode –nodekey tmp_file.txt` + +or + +`bootnode –nodekeyhex 77bd02ffa26e3fb8f324bda24ae588066f1873d95680104de5bc2db9e7b2e510 // This should be read 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 From 173f90ca9bfa91cd177c681ed1fe226398d4f6f8 Mon Sep 17 00:00:00 2001 From: Tyrone Lobban Date: Fri, 10 Feb 2017 16:09:54 +0000 Subject: [PATCH 2/5] Update running.md --- docs/running.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/running.md b/docs/running.md index 71c2c2bc7bf7..4210f5bcf5b5 100644 --- a/docs/running.md +++ b/docs/running.md @@ -106,7 +106,7 @@ 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 you can use when starting up a Node in order that new peers will be auto-added to the network. You will need to generate a bootnode key and enode: +Optionally you can set up a bootnode that all the other nodes first connect to in order to find other peers in the network. You will need to generate a bootnode key and enode: 1- To generate the key for the first time: From 18add7d77fe9deef8f97152b5821f946c784179f Mon Sep 17 00:00:00 2001 From: Tyrone Lobban Date: Fri, 10 Feb 2017 16:40:33 +0000 Subject: [PATCH 3/5] Document bootnode setup process --- docs/running.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/running.md b/docs/running.md index 4210f5bcf5b5..bb1fb6c4dbb9 100644 --- a/docs/running.md +++ b/docs/running.md @@ -106,11 +106,11 @@ 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 first connect to in order to find other peers in the network. You will need to generate a bootnode key and enode: +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 need to generate a bootnode key and enode: -1- To generate the key for the first time: +1- To generate the key and enode for the first time: -`bootnode –genkey tmp_file.txt //this will generate a key inside a “tmp_file.txt” file` +`bootnode –genkey tmp_file.txt //this will generate a key and enode url inside a “tmp_file.txt” file` 2- To start using the key and start your bootnode: From de2594f3919985560fcb6b4f3e9846059b4fa13f Mon Sep 17 00:00:00 2001 From: Tyrone Lobban Date: Fri, 10 Feb 2017 17:18:27 +0000 Subject: [PATCH 4/5] Fix bootnode enode comment Correct the documentation on the bootnode keygen --- docs/running.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/running.md b/docs/running.md index bb1fb6c4dbb9..fa6998093854 100644 --- a/docs/running.md +++ b/docs/running.md @@ -106,15 +106,15 @@ 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 need to generate a bootnode key and enode: +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 and enode for the first time: +1- To generate the key for the first time: -`bootnode –genkey tmp_file.txt //this will generate a key and enode url inside a “tmp_file.txt” file` +`bootnode –genkey tmp_file.txt //this will generate a key inside a “tmp_file.txt” file` 2- To start using the key and start your bootnode: -`bootnode –nodekey tmp_file.txt` +`bootnode –nodekey tmp_file.txt // start the bootnode and output the enode url` or From b2c13981488e840a271a9f3cd784442185a49eb5 Mon Sep 17 00:00:00 2001 From: Tyrone Lobban Date: Fri, 10 Feb 2017 22:01:00 +0000 Subject: [PATCH 5/5] Clarify bootnode start command --- docs/running.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/running.md b/docs/running.md index fa6998093854..90641a00ca49 100644 --- a/docs/running.md +++ b/docs/running.md @@ -110,15 +110,15 @@ Optionally you can set up a bootnode that all the other nodes will first connect 1- To generate the key for the first time: -`bootnode –genkey tmp_file.txt //this will generate a key inside a “tmp_file.txt” file` +`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 start using the key and start your bootnode: +2- To later restart the bootnode using the same key (and hence use the same enode url): -`bootnode –nodekey tmp_file.txt // start the bootnode and output the enode url` +`bootnode –nodekey tmp_file.txt` or -`bootnode –nodekeyhex 77bd02ffa26e3fb8f324bda24ae588066f1873d95680104de5bc2db9e7b2e510 // This should be read from tmp_file.txt` +`bootnode –nodekeyhex 77bd02ffa26e3fb8f324bda24ae588066f1873d95680104de5bc2db9e7b2e510 // Key from tmp_file.txt` ### Start node