What's it going to take to add a bolt-12 offer to my nostr profile so that it's used for zaps?
Discussion
We’d need a new nip for bolt12 zaps. I still don’t understand how that would even be possible. There needs to be a way to send information with the payment about what you’re zapping. Currently, we send that information when requesting the invoice, but that step doesn’t exist with a bolt12 payment.
Hmm ya maybe it's way harder than it seems, as is most things in Bitcoin 🫣
I took a quick look at https://nostr.how/en/zaps and I think the payer's nostr app needs to pass to the payer's Lightning app via an API call:
- the static invoice of the note's poster
- an ID for the zap that the payer's LN app should include as a note with the payment
- the sats amount the payer selected
The zapper's nostr app can then post a note about the zap with the ID, amount and relays to respond to. This should be possible without nostr specific changes to Lightning clients.
The note lets the zap receiver know what note was zapped. I'm not sure how the zap receiver can confirm the zap though. They would need their Nostr app to query their Lightning app.. or maybe the other way around?
Then they can post the confirmation note to the relays specified by the sender.
So you’d need more than just a bolt12 offer to know how to communicate with the lightning app, right? Sounds more complicated than the current spec which simply requires a lightning address.
I think it's a matter of if you can support the LN address functionality via standardized LN wallet API. Could take awhile but we need something similar to support Ocean mining payouts so could be it happens sooner rather than later.