From 9735bbfd15e510b3c35a41882ca5f80805a85931 Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Thu, 28 Mar 2024 19:24:41 -0400 Subject: [PATCH] Changed the relay requirements of checking ptag from SHOULD to MAY --- 59.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/59.md b/59.md index 65ca6f48..71c5eb28 100644 --- a/59.md +++ b/59.md @@ -48,7 +48,7 @@ Tags MUST always be empty. 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 @@ -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. -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. - -Relays SHOULD 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. +To maximize privacy: +1. `.created_at` MAY not be accurate. +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. +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 to attach a certain amount of proof-of-work to the wrapper event per [NIP-13](13.md) in a bid to demonstrate that