From c012b1cf52e54245f25d6d509065989e414accc7 Mon Sep 17 00:00:00 2001 From: "myarbrough@oreilly.com" Date: Wed, 5 Nov 2014 08:58:36 -0800 Subject: [PATCH] Made changes to ch04.asciidoc --- ch04.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ch04.asciidoc b/ch04.asciidoc index 6bf11ec0..31c7c775 100644 --- a/ch04.asciidoc +++ b/ch04.asciidoc @@ -743,10 +743,11 @@ To make the index number easier to read and display, the index number for harden ===== HD wallet key identifier (path) -Keys in an HD wallet are identified using a "path" naming convention, with each level of the tree separated by a slash (/) character (see Table 4-8). Private keys derived from the master private key start with "m". Public keys derived from the master public key start with "M". Therefore, the first child private key of the master private key is m/0. The first child public key is M/0. The second grandchild of the first child is m/0/1, and so on. +Keys in an HD wallet are identified using a "path" naming convention, with each level of the tree separated by a slash (/) character (see <>). Private keys derived from the master private key start with "m". Public keys derived from the master public key start with "M". Therefore, the first child private key of the master private key is m/0. The first child public key is M/0. The second grandchild of the first child is m/0/1, and so on. The "ancestry" of a key is read from right to left, until you reach the master key from which it was derived. For example, identifier m/x/y/z describes the key that is the z-th child of key m/x/y, which is the y-th child of key m/x, which is the x-th child of m. +[[table_4-8]] .HD wallet path examples |======= | m/0 | The first (0) child private key from the master private key (m)