mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-23 08:55:52 -05:00
doc: add BIP32
This commit is contained in:
parent
b1a241b0b0
commit
1d4977b12c
7
704.md
7
704.md
|
@ -17,3 +17,10 @@ This means that each participant has to:
|
||||||
- build a `direct message top key` from which it will derive keys to send `kind:4` events and keys where to recieve (listen for) `kind:4` events
|
- build a `direct message top key` from which it will derive keys to send `kind:4` events and keys where to recieve (listen for) `kind:4` events
|
||||||
- share this `direct message top key` with its DM peer
|
- share this `direct message top key` with its DM peer
|
||||||
|
|
||||||
|
Each client has a `master` key (denoted with `m`). This key can be the profile `nsec...`, but it is not mandatory.
|
||||||
|
|
||||||
|
## BIP32 purpose
|
||||||
|
[https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki](BIP32) is used to derive the paths.
|
||||||
|
|
||||||
|
This NIP defines purpose `25709` (`dm` -> `0x646d` -> `25709`) for deriving `Direct Messages` related keys.
|
||||||
|
`m/25709'/1237'/[<account>']`
|
Loading…
Reference in New Issue
Block a user