ZIP 316: Clarify position of Transparent IVKs in the key tree.

Co-authored-by: Kris Nuttycombe <kris.nuttycombe@gmail.com>
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Deirdre Connolly 2021-12-08 16:29:56 -05:00 committed by Daira Hopwood
parent 110fe1a84e
commit 96c5ad3f69
1 changed files with 3 additions and 2 deletions

View File

@ -417,8 +417,9 @@ The following FVK or IVK Encodings are used in place of the
same as the last 65 bytes of the extended public key format defined same as the last 65 bytes of the extended public key format defined
in section “Serialization format” of BIP 32 [#bip-0032-serialization-format]_.) in section “Serialization format” of BIP 32 [#bip-0032-serialization-format]_.)
However, the FVK uses the key at the Account level, i.e. at path However, the FVK uses the key at the Account level, i.e. at path
:math:`m / 44' / coin\_type' / account'`, while the IVK uses its :math:`m / 44' / coin\_type' / account'`, while the IVK uses the
non-change child key at path :math:`m / 44' / coin\_type' / account' / 0`. external (non-change) child key at the Change level, i.e. at path
:math:`m / 44' / coin\_type' / account' / 0`.
The Human-Readable Parts (as defined in [#bip-0350]_) of Unified Viewing The Human-Readable Parts (as defined in [#bip-0350]_) of Unified Viewing
Keys are defined as follows: Keys are defined as follows: