why do current zaps need custodians or middlemen? It’s slightly easier but you still need to run a node which most people won’t do. I think the “bolt12 will make things more decentralized” meme is a bit over-optimistic. The only thing it does is not require a web server, but thats not even the hardest part, and is even not needed because of services like which i use for my noncustodial zaps. Also, how do web clients fetch the invoice? Even if you use my lnsocket library, you still need a publicly routable node to serve the offer request, then your back to nwc invoice fetching or something which is way better for decentralization View quoted note →

Replies (9)

I spent a good year trying to make zaps work with bolt12 like two years ago and decided against it. I don’t understand why people are so pro bolt12 now, I can’t see how it improves zaps that much at all. nwc invoice fetching would be way better: any node could implement it now, wouldn’t have home firewall issues, no webserver required, web clients could use it. It is substantially better for zapping than bolt12
> you still need to run a node which most people won’t do Zeus, Phoenix and Breez are nodes in your phone that are easy to run for most people. The two first already support BOLT12. You are probably right about NWC but I've mostly seen it used to make payments, not request invoices.
I don’t see how those could support serving offer requests if they are not open. You couldn’t use that for zaps.
You don't need to *ask* a public node to route for you, they can't really tell you're using them this way. The web->LN issue is real: no certs, no web for you! Getting an invoice without waking the node seems to require PTLCs.
yeah bolt12 is great, but I hope a zaps v2 spec is more nwc focused and supports more types of payments (like ecash, etc)