From 6e10e94e3cd3ee81cc98a3aa2b1c6f1ba147c1a5 Mon Sep 17 00:00:00 2001 From: Vlad Stan Date: Mon, 10 Apr 2023 09:26:38 +0300 Subject: [PATCH] doc: update motivation --- 704.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/704.md b/704.md index af39d06..1860969 100644 --- a/704.md +++ b/704.md @@ -9,7 +9,9 @@ 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. + +This NIP describes a way to obfuscate DM communications from the "general public", it does not deal with the relay tracking of clients (for that see [NIP XXX](xxx)). ## 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. @@ -23,4 +25,4 @@ Each client has a `master` key (denoted with `m`). This key can be the profile ` [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 +`m/25709'/1237'/[']`