2024-05-24 16:58:40 -04:00
NIP-62
======
Right to Vanish
---------------
`draft` `optional`
This NIP offers a Nostr-native way to request a complete reset of a key's fingerprint on the web. In some jurisdictions, this is a legally binding procedure and thus supporters of this NIP MUST trully delete events from their database.
2024-06-03 18:47:59 -04:00
## Delete My Content
2024-05-24 16:58:40 -04:00
2024-05-28 16:58:28 -04:00
Kind `62` informs a specific relay to delete everything, including [NIP-09 ](09.md ) Deletion Events, from the `.pubkey` until its `.created_at`
2024-05-24 16:58:40 -04:00
```js
{
"kind": 62,
"pubkey": < 32-bytes hex-encoded public key of the event creator > ,
"tags": [
["relay", "< relay url > "]
],
"content": "< reason or note > ",
//...other fields
}
```
The tag list MUST include at least one `relay` value.
Content MAY include a reason or a legal notice to the relay operator.
Relays MUST fully delete any events from the `.pubkey` if their service url is tagged in the event.
2024-05-24 17:03:19 -04:00
Relays MAY store the deletion request for bookkeeping and ensure past events are not re-broadcasted into the relay.
2024-05-24 16:58:40 -04:00
2024-05-28 16:58:28 -04:00
Paid relays or relays that have restrictions on who can post MUST also follow the request regardless of the user's status.
2024-05-24 16:58:40 -04:00
2024-05-28 16:58:28 -04:00
Clients SHOULD send this event to the target relays only.
2024-05-24 16:58:40 -04:00
## Right to Vanish
2024-05-28 17:03:23 -04:00
Kind `62` can also inform ALL relays to delete everything, including [NIP-09 ](09.md ) Deletion Events, from the `.pubkey` until its `.created_at`
2024-05-24 16:58:40 -04:00
```js
{
2024-05-28 16:58:28 -04:00
"kind": 62,
2024-05-24 16:58:40 -04:00
"pubkey": < 32-bytes hex-encoded public key of the event creator > ,
2024-05-28 16:58:28 -04:00
"tags": [
["relay", "ALL_RELAYS"]
],
"content": "< reason > ",
2024-05-24 16:58:40 -04:00
//...other fields
}
```
2024-05-28 16:58:28 -04:00
The tag list MUST include a `relay` with value `ALL_RELAYS` in uppercase.
2024-05-24 16:58:40 -04:00
2024-05-24 21:46:52 -04:00
Content MAY include a reason to the relay operator.
2024-05-24 16:58:40 -04:00
Relays MUST fully delete any events from the `.pubkey` .
2024-05-24 17:03:19 -04:00
Relays MAY store the deletion request for bookkeeping and ensure past events are not re-broadcasted into the relay.
2024-05-24 16:58:40 -04:00
2024-05-28 16:58:28 -04:00
Paid relays or relays that have restrictions on who can post MUST also follow the request regardless of the user's status.
2024-05-24 16:58:40 -04:00
2024-05-28 16:58:28 -04:00
Clients SHOULD broadcast this event to as many relays as possible.