From e8d4ea3b0c5ce273fb6838b70aefba2b9469e76a Mon Sep 17 00:00:00 2001 From: "myarbrough@oreilly.com" Date: Fri, 21 Nov 2014 05:17:48 -0800 Subject: [PATCH] Made changes to ch04.asciidoc --- ch04.asciidoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/ch04.asciidoc b/ch04.asciidoc index 175310f2..001ba054 100644 --- a/ch04.asciidoc +++ b/ch04.asciidoc @@ -82,6 +82,11 @@ KxFC1jmwwCoACiCAWZ3eXa96mBM6tb3TYzGmf6YwgdGWZgawvrtJ The +dumpprivkey+ command opens the wallet and extracts the private key that was generated by the +getnewaddress+ command. It is not otherwise possible for bitcoind to know the private key from the public key, unless they are both stored in the wallet. +[TIP] +===================================================================== +The +dumpprivkey+ command is not generating a private key from a public key, as this is impossible. The command simply reveals the private key that is already known to the wallet and which was generated by the getnewaddress command. +===================================================================== + You can also use the command-line sx tools (see <>) to generate and display private keys with the sx command +newkey+: (((range="endofrange", startref="ix_ch04-asciidoc3")))(((range="endofrange", startref="ix_ch04-asciidoc2")))(((range="endofrange", startref="ix_ch04-asciidoc1"))) ----