Separate keys for bootstrapper and peer

README.md

@@ -10,12 +10,12 @@
 ```
 cd content-dht-provide-find
 make
-./dht-interop -b ../util/private_key.bin
+./dht-interop -b ../util/private_key.bin.bootstrapper.Wa
 ```
 
 `-b` means bootstrap mode.  In this example, the go program is always the bootstrap node, so `-b` is always required.
 
-Note that the node ID of `dht-interop` is always `Qm...6aJ9oRuEzWa` because it is being read in from `../util/private_key.bin` (a private key marshalled to X.509 generated by `util/private-key-gen`).  This is to keep the peer id of the bootstrap server stable across invocations.
+Note that the node ID of `dht-interop` is always `Qm...6aJ9oRuEzWa` because it is being read in from `../util/private_key.bin.bootstrapper.Wa` (a private key marshalled to X.509 generated by the program `util/private-key-gen`).  This is to keep the peer id of the bootstrap server stable across invocations.
 
 **Second terminal:**  run the command printed out by dht-interop, replacing 127.0.0.1 with the IP of the server where dht-interop is listening.  Example: