nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix: links

Browse Source
This commit is contained in:
Vlad Stan 2023-04-07 17:32:31 +03:00
parent 4ad341a2ef
commit c55a29ff6c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
704.md
View File

@ -9,7 +9,7 @@ Key derivation for Encrypted Direct Messages
This NIP defines a way for two clients to derive `one-use-only` keys for sending and recieving `kind:4` events.
## Motivation
The content of `Direct Messages` (NIP-04)[https://github.com/nostr-protocol/nips/blob/master/04.md] is encrypted, but everyone can see who is chatting with whom. This is far from ideal from a privacy perspective.
The content of `Direct Messages` [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) is encrypted, but everyone can see who is chatting with whom. This is far from ideal from a privacy perspective.
## Suggestion
For the maximum of privacy the two participants of a `Direct Message` exchange SHOULD use a different public key for each `kind:4` event.
@ -20,7 +20,7 @@ This means that each participant has to:
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.
[BIP32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) is used to derive the paths.
This NIP defines purpose `25709` (`dm` -> `0x646d` -> `25709`) for deriving `Direct Messages` related keys.
`m/25709'/1237'/[<account>']`