This is why we're asking for keysend support in wallet because most of the V4V music in podcastindex has keysend addresses in them so if the sending wallet doesn't support keysend we can't use them in apps we're building.
Sir Libre's avatar Sir Libre
Thank you for looking into supporting keysend. According to my db at v4vmusic.com approx 95.5% of the music feeds support keysend only. This will open up a vast opportunity for your wallet users to support their favorite artists. image NWC seems to be the way to go. It's been working great for me using albyhub as a proxy to my node. If you can ever get the receiving part of keysend that would be great also. Alby has code for it in it's repo (somewhere) Basically you use a customKey and customValue The payments go to one node. The customKey and customValue tell you the node runner which "account" the payment belongs to. I haven't tried it yet but I believe this is also how lnbits does it. Receiving is a harder problem, so getting sending to work first makes the most sense. Again, Thank You For Your Courage! 🙂
View quoted note →

Replies (2)

I know, is a pain. For this use case, NWC is better than keysend because you can use it with whatever LN node, including a private/mobile one. I strongly suggest also to look into Lightning Pub / ShockWallet for regular users. Lightning Pub is a simple LND node in neutrino mode installed with just one line command and run behind any router, no need for any open ports or Tor or complicated setup. It also use automated liquidity or manual. You connect Shockwallet on multiple devices and is using NWC and CLINK for communications.
Default avatar
Eric P 1 week ago
NWC is a protocol that connects apps to wallets and supports paying invoices and paying keysend. Wallets can choose to support one or the other or preferably both. The reason we prefer keysend is because it doesn't require a bunch of extra LNURL/HTTP infrastructure to make it work. Your wallet pays another wallet directly on the Lightning Network and that's it.