Nostr Web Client

I think people are confused why this is being hailed as a big deal because this has been possible with a custodial lightning wallet since nostr began and several clients have in-app wallets already.

I have a pretty minimal understanding, but I thought the cashu value is on the privacy/offline spending side of things. I’m not sure I understand how it changes onboarding at all.

Freakoverse 1y ago

Aside from the values you mentioned cashu got, the specific value Karnage, I'd imagine, is pointing out is that you don't need to know someone's zap address to send sats, you just need to know their nostr address which is already there / more immediate than their address (if they have one that is).

What does this mean?

When bring a friend over to nostr, or already have friends on here but on different clients, you'd sometimes poke them to make a zap address so you'd send them sats, depending on the client. So what happens is "hey do this, then do that, then.." etc, or reply on specific clients to have their zap address made and the sender dealing with 2 address to send money.

With cashu on nostr, as a send, you'd just need their nostr address and that's it. On the receiver end, assuming there'd be a nostr client that implemented all the 3 wallets and transfer system in a nice UX way that Karnage mentions, wouldn't have to do anything and just see that they've received money.

Reply to this note

Please Login to reply.

Discussion

Mazin 1y ago

But this could be done with a custodial lightning wallet just the same. That’s the confusion.

I could spin up a lightning node and web server at mynewlightningwalletfornostr.com and when anyone makes an lnurl call for an invoice to npub@mynewlightningwalletfornostr.com I’ll provide one and store the sats under that npub internally. When the user eventually comes to claim their sats, they prove they control the npub and the sats are there waiting for them. You can make npubs the internal account system - that part is trivial.