nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-20 06:45:49 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Changed the relay requirements of checking ptag from SHOULD to MAY

Browse Source
This commit is contained in:
Vitor Pamplona 2024-03-28 19:24:41 -04:00
parent 394c77bb11
commit 9735bbfd15
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
59.md
View File

@ -48,7 +48,7 @@ Tags MUST always be empty.
The inner event MUST always be unsigned. The inner event MUST always be unsigned.
To increase privacy, `.created_at` MAY not be accurate. The `extension` tag can be used to minimize the existence of the event after a certain date. To maximize privacy, `.created_at` MAY not be accurate.
## The Gift Wrap Event Kind ## The Gift Wrap Event Kind
@ -68,11 +68,11 @@ A `gift wrap` event is a `kind:1059` event that wraps any other event. `tags` SH
`.content` contains the cyphertext of the [NIP-44](44.md) encryption of the JSON-encoded event. `.content` contains the cyphertext of the [NIP-44](44.md) encryption of the JSON-encoded event.
To increase privacy, `.created_at` MAY not be accurate. The `extension` tag can be used to minimize the existence of the event after a certain date. To maximize privacy:
1. `.created_at` MAY not be accurate.
Relays SHOULD only serve `kind 1059` events intended for the marked recipient based on user AUTH. 2. The `extension` tag can be used to minimize the existence of the event after a certain date.
3. Relays MAY only serve `kind 1059` events intended for the marked recipient based on user AUTH.
Clients SHOULD only send wrapped events to destination relays that offer this protection. 4. Clients MAY only send wrapped events to destination relays that offer this protection.
Relays MAY choose not to store gift-wrapped events due to them not being publicly useful. Clients MAY choose Relays MAY choose not to store gift-wrapped events due to them not being publicly useful. Clients MAY choose
to attach a certain amount of proof-of-work to the wrapper event per [NIP-13](13.md) in a bid to demonstrate that to attach a certain amount of proof-of-work to the wrapper event per [NIP-13](13.md) in a bid to demonstrate that