|
|
|
@ -1450,7 +1450,7 @@ because the possibilities for internal organization into branches and
|
|
|
|
|
subbranches are endless.
|
|
|
|
|
|
|
|
|
|
Two BIPs offer a solution to this complexity by creating some proposed
|
|
|
|
|
standards for the structure of HD wallet trees. BIP43 proposes the use
|
|
|
|
|
standards for the structure of HD wallet trees. ((("BIP43 HD wallet tree structure")))BIP43 proposes the use
|
|
|
|
|
of the first hardened child index as a special identifier that signifies
|
|
|
|
|
the "purpose" of the tree structure. Based on BIP43, an HD wallet
|
|
|
|
|
should use only one level-1 branch of the tree, with the index number
|
|
|
|
@ -1459,7 +1459,7 @@ defining its purpose. For example, an HD wallet using only branch
|
|
|
|
|
m/i++'++/ is intended to signify a specific purpose and that
|
|
|
|
|
purpose is identified by index number "i."
|
|
|
|
|
|
|
|
|
|
Extending that specification, BIP44 proposes a multiaccount structure
|
|
|
|
|
Extending that specification, ((("BIP44 HD wallet tree structure")))BIP44 proposes a multiaccount structure
|
|
|
|
|
as "purpose" number +44'+ under BIP43. All HD wallets following the
|
|
|
|
|
BIP44 structure are identified by the fact that they only used one
|
|
|
|
|
branch of the tree: m/44'/.
|
|
|
|
|