Ecash zaps:

- Receiver (R) announces on their nostr profile which mints they're on

- R posts something dope on nostr

- Sender (S) mints P2PK-locked ecash from R's mint to R's nostr pubkey

- S attaches locked ecash to R's post

- Observer (O) sees ecash attached to R's note and verifies P2PK lock ("receiver is R") and DLEQ proof ("ecash is legit").

- O's nostr client shows "1234 sats zapped from S to R"

Reply to this note

Please Login to reply.

Discussion

Crazy cool does this work on Damus or just Snort

It doesn't work anywhere unfortunately, I couldn't find the time to write the nostr spec and implement the necessary things in Cashu-TS, but the Cashu protocol is already there :)

guess I need to finish nut-11 implementation

This is missing double spending protection, the same valid ecash could be sent to a bunch of notes of the same author, the sender only looses 1 sat, but an observer sees 100000 sat zaps.

That's true, hadn't thought about that.

It should be easy to commit to the note ID inside the ecash note!

That should work.

i wonder if there’s a way to do this without having R specify mints in their profile. then it would be just like spending to a bitcoin address which would be crazy

receiving i should say*