I know how to make a very cool alternative to Nostr zaps using Cashu but before we can tackle that, we need to add some more crypto magic to the protocol which we're already working on.
Requirements:
- Tokens that everyone can verify the signature of (DLEQ proofs).
- Tokens that can be locked to a specific recipient (P2SH/P2PK).
Receiver can remain offline, sender can pay with a Lightning wallet to mint tokens that can be attached to a Nostr note and later redeemed by the recipient when they come back online.
Login to reply
Replies (17)
I would think because ecash is just a string of text so if you can transmit text on nostr, you can send ecash.
๐
View quoted note โ
Let's go! ๐
View quoted note โ
Yes, but what is the usecase? What can this do better, differently than the already available lightning?
I want this to happen. ๐ฅ๐ฅ๐ฅ
YES!
Private transactions and 0 fees.
Nothing of value is truly free.
You will pay a fee when you convert back to lightning, though.
This is a great idea.
Yes, that's the thing that we're still hashing out. Tokens can be locked to a recipient and have a timelock, like an HTLC.
it's more private, asynchronous, and it doesn't require you to run a lightning node or have a custodial wallet
An LN invoice is also just a text string. The difference is in how you redeem it. The LN invoice requires your lightning node to talk to their lightning node synchronously, so it requires you both to run an always-online server. Most nostr users get around this requirement by using a custodial wallet. Lots of lightning stans complain about this, but you can't get around the reality of LN zaps requiring a lightning node. It's baked into the technology.
Ecash obviates the need for sender and receiver to run an always-on server. Instead, the ecash mint serves as a single always-on server in between sender and receiver. But wait! It gets better! The ecash server cannot tell who is transacting. In other words, this solves the non-custodial zap wallet problem and improves privacy to boot.
Feels like a nice upgrade
๐ฏ
Couldn't a bot solve the zap issue for Damus? Instead of a button, iPhone users could delegate the zapping process by replying to messages mentioning a pre-configured bot. @jb55
Excellent, looking forward to seeing what you come up with.