{"id":"1ec18e39448f909d6de0b8e20d1787556a68ed40f2ad14a065d1f4bb6cd3c119","pubkey":"2b39b4ffe62933df970e19366c22c1e092f953f83fcfed754e0f04d5a3b459f9","created_at":1781353189,"kind":30817,"tags":[["d","nip-62"],["title","NIP-62: Request to Vanish"],["summary","Kind 62, a request that a relay delete everything a key ever published there."],["s","draft"],["t","nostr"],["t","nip"],["k","62","Request to Vanish"],["alt","A specification: NIP-62: Request to Vanish"],["client","openspecs-import"],["published_at","1739934516"],["proxy","https://github.com/nostr-protocol/nips/blob/656cecc7c0a815b6a2b218d3b5d6f078b3f4dbab/62.md","web"],["x","ba63094da240a0dd4f2bd4c7bb878d09e92c4af32fc40fa84cac5fdf88a5d899"]],"content":"NIP-62\n======\n\nRequest to Vanish\n-----------------\n\n`draft` `optional` `relay`\n\nThis NIP offers a Nostr-native way to request a complete reset of a key's fingerprint on the web. This procedure is legally binding in some jurisdictions, and thus, supporters of this NIP should truly delete events from their database. \n\n## Request to Vanish from Relay\n\nKind `62` requests a specific relay to delete everything, including [NIP-09](nostr:naddr1qvzqqqrcvypzq2eeknl7v2fnm7tsuxfkds3vrcyjl9fls070a465urcy6k3mgk0eqqrxu6ts95crjpl6tec) Deletion Events, from the `.pubkey` until its `.created_at`. \n\n```yaml\n{\n  \"kind\": 62,\n  \"pubkey\": <32-byte hex-encoded public key of the event creator>,\n  \"tags\": [\n    [\"relay\", \"<relay url>\"]\n  ],\n  \"content\": \"<reason or note>\",\n  //...other fields\n}\n```\n\nThe tag list MUST include at least one `relay` value. \n\nContent MAY include a reason or a legal notice to the relay operator. \n\nRelays MUST fully delete any events from the `.pubkey` if their service URL is tagged in the event. \n\nRelays SHOULD delete all [NIP-59](nostr:naddr1qvzqqqrcvypzq2eeknl7v2fnm7tsuxfkds3vrcyjl9fls070a465urcy6k3mgk0eqqrxu6ts956njrwwjk6) Gift Wraps that p-tagged the `.pubkey` if their service URL is tagged in the event, deleting all DMs to the pubkey.\n\nRelays MUST ensure the deleted events cannot be re-broadcasted into the relay. \n\nRelays MAY store the signed request to vanish for bookkeeping.\n\nPaid relays or relays that restrict who can post MUST also follow the request to vanish regardless of the user's status. \n\nPublishing a deletion request event (Kind `5`) against a request to vanish has no effect. Clients and relays are not obliged to support \"unrequest vanish\" functionality.\n\nClients SHOULD send this event to the target relays only. \n\n## Global Request to Vanish\n\nTo request ALL relays to delete everything, the event MUST include a `relay` tag with the value `ALL_RELAYS` in uppercase. \n\n```yaml\n{\n  \"kind\": 62,\n  \"pubkey\": <32-byte hex-encoded public key of the event creator>,\n  \"tags\": [\n    [\"relay\", \"ALL_RELAYS\"]\n  ],\n  \"content\": \"<reason>\",\n  //...other fields\n}\n```\n\nClients SHOULD broadcast this event to as many relays as possible. \n","sig":"5008ffd8518e35ac1896f10117151baa494fe8f4e4e9deb7c152af5a1e5ba7a9018d4d4fc107175b8090869f3bffdab8580f66e81fb31596ff08559f1c699882"}