Skip to content

NIP-09-PR: allow gift wrap recipients to request deletion of their own copy#2350

Open
geralt-debugs wants to merge 2 commits into
nostr-protocol:masterfrom
geralt-debugs:participant_self_removal
Open

NIP-09-PR: allow gift wrap recipients to request deletion of their own copy#2350
geralt-debugs wants to merge 2 commits into
nostr-protocol:masterfrom
geralt-debugs:participant_self_removal

Conversation

@geralt-debugs
Copy link
Copy Markdown

@geralt-debugs geralt-debugs commented May 17, 2026

NIP-09 currently requires that the pubkey of a kind:5 deletion request match the pubkey of the event being deleted. This works for events a user creates, but not for gift wraps (kind:1059), which are authored by an ephemeral random key even though they are addressed to a specific recipient via a p tag.

This PR extends NIP-09 to allow a gift wrap recipient to request deletion of their own copy. The rule is narrow and explicit: a kind:5 event may reference a kind:1059 event when the requester's pubkey appears in a p tag of that gift wrap and the k tag is "1059". In all other cases the existing NIP-09 author-matching rule is unchanged.

Since each NIP-17 recipient receives a separately-wrapped copy of a message, deleting one user's gift wrap has no effect on copies addressed to others. No new event kind is introduced.

Use cases

  1. Users might want to remove spam from their inboxes/invites/etc
  2. Users might simply want to cleanup their inboxes/invites/etc
  3. Users might want to delete a message sent by someone else

Comment thread 09-PR.md Outdated
@geralt-debugs geralt-debugs changed the title NIP-09-PR: kind 84 participant self-removal NIP-09-PR: participant self-removal May 31, 2026
@geralt-debugs geralt-debugs changed the title NIP-09-PR: participant self-removal NIP-09-PR: allow gift wrap recipients to request deletion of their own copy May 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants