Replying to Avatar jb55

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 https://sendsats.lol 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 nostr:note1nflxn2l39t5phz7eqnc2u076jgs00f9kw0xxgdqcdwy86szv5hgq0fuwqu

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

Reply to this note

Please Login to reply.

Discussion

Do you know if more wallets are planning to implement nwc?

i doubt it, this would be more for zapping, but maybe ? different use cases

Found this https://github.com/ACINQ/phoenix/issues/537 they specifically mention zapping. I guess it also depends if we're talking about sending or receiving?

I love zaps, but NWC enables way more than zaps. It is enabling a whole ecosystem through the ease of connecting apps to wallets https://github.com/getAlby/awesome-nwc

agree with everything although I'd like to add that bolt12 is fucking cool, it just doesn't improve zapping really.

yeah bolt12 is great, but I hope a zaps v2 spec is more nwc focused and supports more types of payments (like ecash, etc)