NIP-09 - add NIP-17 Enable deletion request for holder of pubkey destination?

[trbouma]

Is it possible to add deletion requests for NIP-17 based on what pubkey the message is encrypted to?

It offsets an attack where an attacker sends me unwanted messages, then claims I have read them. Under duress, I am forced to reveal the messages.

Giving NIP-17 deletion request doesn't go the full way, but I would eventually support only relays that enable this for me.

Rationale - I am using NIP-17 to transmit/receive ecash and sensitive records. I want them to disappear at my own action or over time.

Whaddya think?

[trbouma]

I am also experimenting with an event kind 21059 which I am calling TemporaryGiftWrap - an ephemeral event that meets my requirements as well.

[vitorpamplona]

DM Inbox relays do delete gift wraps that p-tag the key requesting the deletion. I think that should be the standard for giftwraps.

[staab]

Yes, and I agree even though I used to be opposed to it because it breaks shared keys. But we can just use a different kind if that becomes necessary.

[mikedilger]

I don't see in NIP-17 or NIP-09 anything about relays deleting. In fact NIP-09 deletions are for clients, relays just pass on the request.

I'm in favor of this and I think we need to spell it out somewhere.

[trbouma]

Thanks for the comments everyone. I am implementing a secure record transmittal and secure auth capability that uses NIP-59/44 and a variant of NIP-17 (events other than 1059) - not yet fully baked and exploring requirements that might land in a NIP.