Nostr Web Client

we could implement it but it wouldn't have zaps, as there is no spec for that yet. the only usecase I can see is profile tipping with no-zap? That's not a huge priority for us.

One thing we could do is make a spec for adding a bolt12 to your profile, but we would still need some code that connects to the lightning network and fetches a bolt12 invoice from a bolt12 offer.

This is a nontrivial amount of work for a feature most people won't use, not to mention passing bolt12 invoices for payment wouldn't work for most wallets yet, or even any NWC wallet.

Gregor 1y ago

How does fetching an invoice from a BOLT12 offer differ from fetching an invoice from a lightning address?

If you could fetch the invoice, what else would you need to create a Zap?

Reply to this note

Please Login to reply.

Discussion

jb55 1y ago

fetching an invoice from a lightning address is a simple HTTPS call, fetching an invoice from an offer requires you to connect to a lightning node directly.

luckily I have a library that does just that: https://github.com/jb55/lnsocket

but to do onion routing is non-trivial, so you would only be able to fetch direct-hop invoices atm.

Gregor 1y ago

I see, that evidently makes it considerably more challenging. I appreciate you taking the time to explain, thanks.

Do you generally see BOLT12 as a practical way to transition Zaps to non custodial transactions, or do you find it too complex for the purpose?

jb55 1y ago

The main thing it does is reduce the burden on running an http server in conjunction with your lightning node. I would argue running an http server is the least hard thing, running a lightning node itself is more complex, but things like phoenix make running an ln node easy, so it may be worth switching to it.