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

clarify the various types of child keys derived from an identity

Browse Source
This commit is contained in:
Justus Ranvier 2015-12-18 10:47:44 -06:00
parent 876af7fa87
commit 07ab320513
No known key found for this signature in database
GPG Key ID: 2A5FDA70EAD9E623
1 changed files with 22 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
bip-0047.mediawiki
View File

@ -31,9 +31,29 @@ Payment codes add identity information to transactions which is useful in a merc
We define the following 3 levels in BIP32 path: We define the following 3 levels in BIP32 path:
<pre> <code>
m / purpose' / coin_type' / identity' m / purpose' / coin_type' / identity'
</pre> </code>
The child keys derived from an identity are used in different ways:
<code>
m / purpose' / coin_type' / identity' / 0
</code>
The 0th (non-hardened) child is the notification key.
<code>
m / purpose' / coin_type' / identity' / 0 through 2147483647
</code>
These (non-hardened) keypairs are used for ECDH to generate deposit addresses.
<code>
m / purpose' / coin_type' / identity' / 0' through 2147483647'
</code>
These (hardened) keypairs are ephemeral payment codes.
Apostrophe in the path indicates that BIP32 hardened derivation is used. Apostrophe in the path indicates that BIP32 hardened derivation is used.