From c55a29ff6cf7f6a41297a4d41e7f99246bda7a7a Mon Sep 17 00:00:00 2001 From: Vlad Stan Date: Fri, 7 Apr 2023 17:32:31 +0300 Subject: [PATCH] fix: links --- 704.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/704.md b/704.md index abe67d6..af39d06 100644 --- a/704.md +++ b/704.md @@ -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'/[']` \ No newline at end of file