bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

minor cleanups

Browse Source
This commit is contained in:
Daniel Weigl 2016-06-14 14:54:41 +02:00
parent b1e7db5376
commit babd604cc4
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
bip-p2sh-accounts.mediawiki
View File

@ -22,20 +22,22 @@ will detect the account and handle them appropriately.
===Considerations===
Two generally different approaches are possible for current BIP44 capable wallets:
1) Allow the user to use the same account(s) that they already uses, but add segregated witness encoded addresses to it
1.1) Use the same public keys as defined in BIP44, but in addition to the normal P2PKH address also derive the P2SH address from it.
1.2) Use the same account root, but branch off and derive different external and internal chain roots to derive dedicated public keys for the segregated witness addresses.
1) Allow the user to use the same account(s) that they already uses, but add segregated witness encoded addresses to it
2) Create dedicated accounts only used for segregated witness addresses.
1.1) Use the same public keys as defined in BIP44, but in addition to the normal P2PKH address also derive the P2SH address from it.
The solutions from point 1 have a common disadvantage: if a user imports/recovers a BIP<ThisBipNumber>-compatible wallet masterseed into/in a non-BIP<ThisBipNumber>-compatible wallet, the account might show up but also it might miss some UTXOs.
Thus this BIP uses solution 2, which fails in a more visible way. Either the account shows up or not at all. The user does not have to check his balance after using the same seed in different wallets.
1.2) Use the same account root, but branch off and derive different external and internal chain roots to derive dedicated public keys for the segregated witness addresses.
2) Create dedicated accounts only used for segregated witness addresses.
The solutions from point 1 have a common disadvantage: if a user imports/recovers a BIP<ThisBipNumber>-compatible wallet masterseed into/in a non-BIP{ThisBipNumber}-compatible wallet, the account might show up but also it might miss some UTXOs.
Therefore this BIP uses solution 2, which fails in a more visible way. Either the account shows up or not at all. The user does not have to check his balance after using the same seed in different wallets.
==Specifications==
This BIP defines the two needed steps to derive multiple deterministic addresses based on a [[bip-0032.mediawiki|BIP 32]]
root account.
This BIP defines the two needed steps to derive multiple deterministic addresses based on a [[bip-0032.mediawiki|BIP 32]] root account.
===Public key derivation===
@ -47,7 +49,7 @@ serialization method.
m / purpose' / coin_type' / account' / change / address_index
</pre>
For the `purpose`-path level it uses <ThisBipNumber>'. The rest of the levels are used as defined in BIP44
For the `purpose`-path level it uses {ThisBipNumber}'. The rest of the levels are used as defined in BIP44
===Address derivation===
@ -84,7 +86,6 @@ To derive the P2SH address from the above calculated public key, we use the enca
address = base58check(prefix | addressBytes) = 1xyz....
</pre>
...
==Reference==