From be4e57f01b35d8108ebb1c405f1956cd21967c05 Mon Sep 17 00:00:00 2001 From: Alex Waters Date: Sun, 13 Jul 2014 19:43:53 -0400 Subject: [PATCH] 'key' to 'keyspace' The term 'keyspace' more accurately reflects the nature of this statement. --- ch04.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch04.asciidoc b/ch04.asciidoc index 6894d163..4e80921a 100644 --- a/ch04.asciidoc +++ b/ch04.asciidoc @@ -70,7 +70,7 @@ Below is a randomly generated private key shown in hexadecimal format (256 binar [TIP] ==== -The size of bitcoin's private key, 2^256^ is an unfathomably large number. It is approximately 10^77^ in decimal. The visible universe is estimated to contain 10^80^ atoms. +The size of bitcoin's private keyspace, 2^256^ is an unfathomably large number. It is approximately 10^77^ in decimal. The visible universe is estimated to contain 10^80^ atoms. ==== To generate a new key with the Bitcoin Core Client (see <>), use the +getnewaddress+ command. For security reasons it displays the public key only, not the private key. To ask bitcoind to expose the private key, use the +dumpprivkey+ command. The +dumpprivkey+ shows the private key in a base-58 checksum encoded format called the Wallet Import Format (WIF), which we will examine in more detail in <>. Here's an example of generating and displaying a private key using these two commands: