It is disingenuous to call stealth addresses the recipients address. They are addresses that are derived from the recipients address but can’t be tied back to the receiver except by the receiver themselves, so point 2 is basically a lie the way most people would interpret it.

Payment channels are not even a contender for privacy in comparison. Unless this new channel uses some technology im unaware of, it’s using Lightning’s centralized, easily monitored tunnels. No reason to put a bandaid on top of a already flawed system

Reply to this note

Please Login to reply.

Discussion

It is not disingenuous. The recipient alone has the private key; it's his address, whose else would it be? Point 2 is the honest truth: the sender puts the recipient's address in plaintext on the blockchain and if the recipient ever decides to send it he has to identify it on the blockchain again as a possible sender

This is just so rich for someone saying to use a network with notoriously terrible receiver privacy, amount privacy that isn't guaranteed by larger nodes, and IP that is exposed by default to others on the network

But none of the above really matters if the vast majority of lightning users are on on custodial wallets that see everything

https://zapalytics.com/

nostr:nprofile1qqszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagpz4mhxue69uhkummnw3ezummcw3ezuer9wchszyrhwden5te0dehhxarj9ekk7mf0qy88wumn8ghj7mn0wvhxcmmv9uynmh4h

It's important to be completely factual, and factually complete. Factually complete is harder than being completely factual.

To be more charitable I do like lightnings ephemeral nature nostr:npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399s and think that aspect of lightning is great

Lightning doesn't have terrible receiver privacy despite false claims to the contrary. Bolt11 "invoices" had terrible privacy by default, but you could (1) manually wrap them (2) manually replace your key with an ephemeral one (3) use keysend instead. Keysend payments never exposed the recipient, but they also didn't give the sender a "proof of payment." Now we have bolt12 as an arising standard that *also* doesn't expose the recipient by default, and *does* give the sender a proof of payment.

Also: the recipient's ip address is not exposed by default. You have to manually configure your network to do port forwarding if you want to show up as a routing node, and that is a big reason why most lightning users do not route payments. And most users who *do* route payments opt to do it over tor so that they *don't* expose their ip address.

Ah I get it now

For those who want the TLDR of your reply: