From b2c13981488e840a271a9f3cd784442185a49eb5 Mon Sep 17 00:00:00 2001 From: Tyrone Lobban Date: Fri, 10 Feb 2017 22:01:00 +0000 Subject: [PATCH] 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 fa69980938..90641a00ca 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