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

Update 103.md

Browse Source
This commit is contained in:
threeseries 2023-05-09 11:22:06 -05:00 committed by GitHub
parent 7e4c30bc1f
commit 282f3c1ab8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
103.md
View File

@ -10,7 +10,11 @@ This NIP defines a kind 16 event which is a kind 4 event (see [NIP-04](04.md) wh
# Motivation and usage
It's well-known that direct message metadata is public on nostr since everyone can see who is messaging whom and when. One solution to this problem is for the entire event including its metadata to be encrypted before being sent. This outer event can be encrypted and signed with a random key pair, thus hiding the true sender of the direct message. On receiving a kind 16 event the client should decrypt both the outer and inner content, displaying the decrypted inner content to the recipient.
It's well-known that direct message metadata is public on nostr since everyone can see who is messaging whom and when. One solution to this problem is for the entire event including its metadata to be encrypted before being sent. This outer event can be encrypted and signed with a random key pair, thus hiding the true sender of the direct message.
Alternatively, one can encrypt the kind 16 with one's own key pair and send to an intermediate pubkey which is responsible for forwarding the message on to the final recipient. This too would provide anonymity as long as the intermediate pubkey is receiving messages from different users, and effort is made to remove correlation based on timing.
On receiving a kind 16 event the client should decrypt both the outer and inner content, displaying the decrypted inner content to the recipient.
# Example:
@ -33,7 +37,7 @@ A kind 4 event:
}
```
After wrapping in kind 16 with a random key pair:
After wrapping in kind 16 with another key pair:
```json
{