mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-11-14 07:49:07 -05:00
65 lines
2.0 KiB
Markdown
65 lines
2.0 KiB
Markdown
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.
|
|
|
|
## Delete Account
|
|
|
|
Kind `62` informs a specific relay to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.created_at`
|
|
|
|
```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.
|
|
|
|
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 regardless of the user's status.
|
|
|
|
Clients SHOULD send this event to the target relays only.
|
|
|
|
## Right to Vanish
|
|
|
|
Kind `62` can also inform ALL relays to delete everything, including [NIP-09](09.md) Deletion Events, from the `.pubkey` until its `.created_at`
|
|
|
|
```js
|
|
{
|
|
"kind": 62,
|
|
"pubkey": <32-bytes hex-encoded public key of the event creator>,
|
|
"tags": [
|
|
["relay", "ALL_RELAYS"]
|
|
],
|
|
"content": "<reason>",
|
|
//...other fields
|
|
}
|
|
```
|
|
|
|
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 regardless of the user's status.
|
|
|
|
Clients SHOULD broadcast this event to as many relays as possible. |