From 2b78cc9304f775b8391f62b7fe61e99a3fdc905b Mon Sep 17 00:00:00 2001 From: Jon Staab Date: Wed, 20 Dec 2023 11:35:12 -0800 Subject: [PATCH] Add clarification about not replacing nip 04 --- 44.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/44.md b/44.md index 5093acd3..8bc40383 100644 --- a/44.md +++ b/44.md @@ -10,6 +10,10 @@ The NIP introduces a new data format for keypair-based encryption. This NIP is v to allow multiple algorithm choices to exist simultaneously. This format may be used for many things, but MUST be used in the context of a signed event as described in NIP 01. +*Note*: this format DOES NOT define any `kind`s related to a new direct messaging standard, +only the encryption required to define one. It SHOULD NOT be used as a drop-in replacement +for NIP 04 payloads. + ## Versions Currently defined encryption algorithms: @@ -30,7 +34,7 @@ event. When applying this NIP to any use case, it's important to keep in mind yo model and this NIP's limitations. For high-risk situations, users should chat in specialized E2EE messaging software and limit use of nostr to exchanging contacts. -On its own, messages sent using this scheme has a number of important shortcomings: +On its own, messages sent using this scheme have a number of important shortcomings: - No deniability: it is possible to prove an event was signed by a particular key - No forward secrecy: when a key is compromised, it is possible to decrypt all previous conversations