laantungir/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-12-09 16:48:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Enhance metadata/timestamp protection guidance in NIP-59 (#2095)

Browse Source
This commit is contained in:
alltheseas
2025-10-27 12:56:47 -05:00
committed by GitHub
parent 6e6b9877b3
commit bcaad2957d
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
59.md
View File

@@ -97,6 +97,9 @@ To protect recipient metadata, relays SHOULD only serve `kind 1059` events inten
When possible, clients should only send wrapped events to `read` relays for the recipient that implement When possible, clients should only send wrapped events to `read` relays for the recipient that implement
AUTH, and refuse to serve wrapped events to non-recipients. AUTH, and refuse to serve wrapped events to non-recipients.
When adding expiration tags to both `seal` and `gift wrap` layers, implementations SHOULD use independent random timestamps for each layer. Using different `created_at` values increases timing variance and helps protect against metadata correlation attacks.
## An Example ## An Example
Let's send a wrapped `kind 1` message between two parties asking "Are you going to the party tonight?" Let's send a wrapped `kind 1` message between two parties asking "Are you going to the party tonight?"