Unifies 62 and 63 into one with ALL_RELAYS

62.md

@@ -10,7 +10,7 @@ This NIP offers a Nostr-native way to request a complete reset of a key's finger
 
 ## Delete Account
 
-Kind `62` informs a specific relay to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.createdAt`
+Kind `62` informs a specific relay to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.created_at`
 
 ```js
 {
@@ -32,32 +32,34 @@ Relays MUST fully delete any events from the `.pubkey` if their service url is t
 
 Relays MAY store the deletion request for bookkeeping and ensure past events are not re-broadcasted into the relay. 
 
-Paid relays or relays that have restrictions on who can post MUST also follow the request even if the key has not been paid to get access to the relay. 
+Paid relays or relays that have restrictions on who can post MUST also follow the request regardless of the user's status. 
 
-Kind `62` SHOULD only be sent to the target relays. 
+Clients SHOULD send this event to the target relays only. 
 
 ## Right to Vanish
 
-Kind `63` informs ALL relays to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.createdAt`
+Kind `62` informs ALL relays to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.created_at`
 
 ```js
 {
-  "kind": 63,
+  "kind": 62,
   "pubkey": <32-bytes hex-encoded public key of the event creator>,
-  "tags": [],
-  "content": "<reason or note>",
+  "tags": [
+    ["relay", "ALL_RELAYS"]
+  ],
+  "content": "<reason>",
   //...other fields
 }
 ```
 
-The tag list MUST be empty.
+The tag list MUST include a `relay` with value `ALL_RELAYS` in uppercase. 
 
 Content MAY include a reason to the relay operator. 
 
 Relays MUST fully delete any events from the `.pubkey`. 
 
 Relays MAY store the deletion request for bookkeeping and ensure past events are not re-broadcasted into the relay. 
 
-Paid relays or relays that have restrictions on who can post MUST also follow the request even if the key has not been paid to get access to the relay. 
+Paid relays or relays that have restrictions on who can post MUST also follow the request regardless of the user's status. 
 
-Kind `63` SHOULD be widely broadcasted. 
+Clients SHOULD broadcast this event to as many relays as possible.