mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-24 15:38:08 +00:00
Edited ch05_wallets.adoc with Atlas code editor
This commit is contained in:
parent
2333e24db5
commit
892654cc03
@ -1450,7 +1450,7 @@ because the possibilities for internal organization into branches and
|
|||||||
subbranches are endless.
|
subbranches are endless.
|
||||||
|
|
||||||
Two BIPs offer a solution to this complexity by creating some proposed
|
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
|
of the first hardened child index as a special identifier that signifies
|
||||||
the "purpose" of the tree structure. Based on BIP43, an HD wallet
|
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
|
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
|
m/i++'++/ is intended to signify a specific purpose and that
|
||||||
purpose is identified by index number "i."
|
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
|
as "purpose" number +44'+ under BIP43. All HD wallets following the
|
||||||
BIP44 structure are identified by the fact that they only used one
|
BIP44 structure are identified by the fact that they only used one
|
||||||
branch of the tree: m/44'/.
|
branch of the tree: m/44'/.
|
||||||
|
Loading…
Reference in New Issue
Block a user