<oembed><type>rich</type><version>1.0</version><title>Ava wrote</title><author_name>Ava (npub1f6…azcka)</author_name><author_url>https://yabu.me/npub1f6ugxyxkknket3kkdgu4k0fu74vmshawermkj8d06sz6jts9t4kslazcka</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Given your infosec background, I&#39;m sure what I am about to say is nothing new for you, so I am mostly speaking to &#34;the room&#34; here.&#xA;&#xA;Yes, Lightning offers better privacy than Bitcoin when set up properly, but it also has a more complex system, equating to a larger attack surface. LN&#39;s privacy features are not automatic; users must understand and manage their privacy settings actively, which can lead to unintentional exposure of transaction details.&#xA;&#xA;A fundamental privacy weakness persists in the asymmetric nature of Lightning transactions—the sender learns extensive details about the receiver&#39;s node, channels, and liquidity, while the receiver learns nothing about the sender. Plus, there&#39;s the persistent hassle of maintaining channel liquidity.&#xA;&#xA;Even with proper setup, Lightning faces critical privacy vulnerabilities against global adversaries who can monitor network traffic—while individual participants can&#39;t see payment details, entities capable of monitoring internet connections can track payment flows by observing message patterns between nodes, making its privacy guarantees fundamentally weak against sophisticated surveillance.&#xA;&#xA;Lightning falls well short of the anonymity provided by Monero with its stealth addresses, ring signatures, and RingCT—and soon, Full-chain Membership Proofs (FCMPs) will fix current vulnerabilities like the Exchange Attack Everywhere (EAE) attack. With FCMPs, every input will have a 100-million anonymity set, up from the current 16 Ring Signatures.&#xA;&#xA;Where privacy is a concern, I still recommend Monero over Lightning for most people, as Monero&#39;s privacy features are built-in on the base layer and work by default.</html></oembed>