I know very little about bold 12 stuff. Do we need consensus around clients on this?
Heyo nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug can we have "BOLT12":" lno1..." as kind 0 metadata field pls.
Discussion
So bold of me.
I have used bolt12 with Phoenix wallet and it works really well in my experience. I was wishing I could put my bolt12 on my nostr profile - it removes some choke points like relying on coinos DNS.
lno1zrxq8pjw7qjlm68mtp7e3yvxee4y5xrgjhhyf2fxhlphpckrvevh50u0qtz0gx0xgmc8l73x4l9xzjl4szup6639ee9p3gaz8ry80sjn8wzv2qsrt3c9x2gns79v88kgkeuns9s5kdvzvr4xrn0j6uravhtugu2ju6rsqv66vhzfn8gq6p3ddakezl378myez03f2eyd0g7980qs5vp2mjrcl2ctr2kqawfcp834tlcj5wasakllsm4aqdrtd5q8fugynp779j6lwc8tfs7qlstkkvjg2f9zq3zygdut5qqjqqqse2guzglzlsahzgvwafrkcmy09c
This is my bolt12 code as an example.
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.
Thank you to someone for the 21 sats on bolt12. 😊
This btw highlights that to make it work like zaps we need something somewhere that sends the nostr event to relays.
bolt12str!
I don't think so. It could just be prioritised if the receiver has a lno1 address in their metadata AND sender has a native or bridged bolt 12 client. The "lno1..." key is static.
Maybe reuse the cryptocurrency_addresses field from the monero forks.
"cryptocurrency_addresses": {
"monero": "...",
"lightning":"...",
...
}
being intrested and reading through this notes comment thread I looked into it and found a site that exsplains bolt12 for ya https://bolt12.org/
Can't wait for nostr to support bolt12 and https://github.com/bitcoin/bips/blob/master/bip-0353.mediawiki
lno1zrxq8pjw7qjlm68mtp7e3yvxee4y5xrgjhhyf2fxhlphpckrvevh50u0qfz3ny93jkrw3j5tncydc8wyw5dh0hfvp96h05kvqaxajkvg30k0qqsrky8zwpajfucywum5tyspgu34zfff6huardn82jutkf6d3p89z3lqqvm0punyrycrzhw3z3f86028ln3lcxexnr998krrqj2ryqdgdxwj0ftjycfvn4hvn5c5p6qtapmhvgwcsrv7q0rz4yv8nx79kg3n0gujcrdmf7yh6nuchzxt2rkqc29wysypdpemgqqs3fv5gnwxcehdsp73cn82xd7ha5
Good question. Following