i get that. once bolt12 works everywhere though, the problem disappears. it's just a transition and growth issue, right?
Discussion
Is a bolt12 address zapable? I don't think so.
it wouldn't be... the spec would need to be updated? that's beyond my knowledge. nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s plz halp?
Remind me again what a Bolt12 address is? š
This is a nice resource
BOLT 12 uses "offers" and "onion messages". BOLT 12 simplifies the payment process while maintaining strong privacy. Whereas BOLT 11 with LN Addresses require a web server to function to generate LNURL invoices.
Once again thank you! šš¼
We literally had to update all lnaddress server implementations to support kind 9735. Without a server tho..
Bolt12s have proof of payment
correct, we did. i would assume something similar would have to happen again to notify nostr of the payment.
the way it is made we have to start from zero again.
we get nowhere if we keep on starting from zero again and again without even trying to build on what has been achieved so far.
It would be an entirely different protocol. Iām not sure how you would do it.