A simple way would be Gordian Envelopes with an elided encrypted field for the content, and upon payment you receive the encryption key, and the non-elided field.
That way it would all be over nostr and you would be able to know that what you're receiving is actually the content you paid for and it wasn't tampered with, without having access to the content in advance.
In fact you could even publish that on nostr, have it attached to your pubkey like all other event types, it just won't be readable without 1 revealing the encrypted content and 2 decrypting that content.
Login to reply
Replies (1)
That's interesting, but you don't actually need a Gordian Envelope for that assurance. The nostr event is signed, so if the event is changed the signature check will fail. The nostr event either contains the ciphertext or a reference to the file; the file is named by its sha256, so if the file was changed the sha256 wouldn't match, which would also invalidate the nostr event's signature.