mirror of
https://github.com/bitcoin/bips.git
synced 2025-01-18 21:35:13 +01:00
clarify the various types of child keys derived from an identity
This commit is contained in:
parent
876af7fa87
commit
07ab320513
@ -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:
|
||||
|
||||
<pre>
|
||||
<code>
|
||||
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.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user