I thought the NIP47 nwc spec was expanded to allow receiving (i.e. being requested an invoice, generating one and sending it) over nostr. Sad that no wallets nor clients picked that up...
Nwc is just a service that uses lnurl behind the scenes. This one inverts everything and brings the Lnurl exchange to Nostr.
I'm talking about this: https://github.com/nostr-protocol/nips/pull/685 These NWC extension has a "make_invoice" request that can entirely replace lnurl. You could just use this to "pay-to-npub" directly if the npub is running a NWC wallet with this capability
I think that is to make an invoice in your own wallet for others to pay. Currently, there is no way for my pubkey to access your NWC server to make an invoice for me to pay. That part still happens via http
Uff you're right, that was a lost opportunity then... I can't watch the vid right now, but why using nostr DMs instead of using NWC-like events? I also wonder about what are the spam defences of this. On a webserver you control, you can add ratelimits, etc. What's stopping someone from hitting 300 different relays asking for 300 different invoices from your LN node?
Yeah the use of the DM is unnecessary. They can just use any other event kind. Ok the spam side, you can apply the same DoS protections on the relay you are going to use to communicate OR on the service that is replying to those messages. DVMs already have some of those defenses up.
So you rely on your chosen relays to not relay spam to your LN node? Seems reasonable
You can give someone a NWC connection with only make_invoice permissions. LNURL is not needed
We need to figure out a way to make that foolproof so that no dev can make the mistake of sharing the same link that has permission to spend. Kinda like sharing an npub and not an nsec.