This is my bolt12 code as an example.
Discussion
Ok but what do we do with this? Can we zap using this instead of an ln address?
yes you can but almost no wallet supports it, only Phoenix and maybe Zeus?
nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygqgalqhxgp9gpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzyrhwden5te0dehhxarj9ekxzmnyqyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueq555fk2 support it but you need cln as backend, with lnd you obtain this
Also Strike supports it 😉 it's not that hard to add if you are on something other than lnd. And even on lnd you can add that afaik with some wrapper library.
The user wallet must support sending to bolt12 addresses. Currently only cln and phoenix i think
Ohhh that sucks :(
Bolt 12 is supported by at least a dozen wallets, and increasing rapidly. Also supported by Strike and Boltz exchange.
also nostr:nprofile1qqst4qyeqenw7zm0fwjsty68h6cnys5jre2xd8ngqpjv5a2j26s78fspzemhxue69uhhyetvv9ujucm0d9hx7uewd9hj75a0pev support bolt12, if you want experiment with something custodial
Yes, exactly. Essentially it uses the lightning network for the communication (instead of TCP/IP + DNS) and retrieving the invoice.
All lightning nodes except for lnd support it.
The Bolt 11 "ln" invoices aren't designed for re-use. Whereas a Bolt12 "lno1..." is a static re-usable key, with native privacy.