As pointed out in the thread, Bolt12 is onion messaging. It's not just similar, it's exactly the same.
By bouncing onion messages around, it adds latency and failure probability with each hop, and this is before even attempting the payment... it's just to fetch the invoice.
Web-based services don't need to trust DNS, they can use signatures too but in a more performant and scalable architecture.
Connecting directly to a lnurl web server exposes traffic metadata to observers.
reply
No, SSL protects the data... It's only observable if you use a bridge.
There are also other projects using nostr relays with end to end encryption
reply
I'm referring to metadata, not the data itself. You connecting to a specific merchant over SSL is enough information in many cases.
reply
Need to obfuscate that type of information is extremely niche, not something that justifies harming reliability of the entire network, that's what vpns etc are for
reply
I agree users should be able to set the number of intermediate hops to zero, and intermediate hops should be paid 1 sat minimum to reduce spam. Defaulting to 1-2 hops helps the privacy for those who need it though.
reply
Thanks for your answer, but you say "BOLT12 is an onion messaging protocol." That's a statement, I've read docs on BOLT12 and didn't see anything on onion routing. Nothing on being slow and unreliable as TOR. No actors of the LN space called it out loud neither.
So I'm sceptical
reply
Onion Messages are literally the first item listed under "Technology" on bolt12.org
reply
I saw that. If it is as reliable as Tor then indeed it's dead on arrival. Routing node admins won't bother with it.
reply