downside is that useable ln clients are centralized. best is blink, and they have kyc. with best i mean, cheapest and easiest to use and mostly works
When you realize that no one really understands LN privacy and that they are also incapable of understanding network-level privacy, you realize that no one in this space really has a clue about privacy, except for nostr:npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399s
- LN is not a blockchain, and since it uses routing like Tor, in most cases it will always be more private than any blockchain, even Monero, simply because LN does not leave public records for later analysis and all information is encrypted, including the amount and routing fee, in the same way as Tor.
- For the recipient, simply use Blinded Paths or LNproxy. You can also combine them in case a client is not compatible with Blinded Paths.
- It's also useless if you use LN, Coinjoin, or Monero and don't protect your privacy at the network level. Your LN node must be behind Tor, and if you use services like LNProxy, do so behind Tor as well.
Discussion
Even then you can get privacy, as you can use wos with an anonymous email, through vpn (I haven't tried it with tor) and use lnproxy so wos doesn't know where you send.
Remember that they by default will never know where you receive from.
With blink you can also use a throwaway phone and then delete it and add an anonymous email.
Remember that in this life everything has a solution except death.
you can, for small amounts. that is not the point though. as technology, lightning is order of magnitude more complex than on chain transactions. this creates an opening for centralized services
The truth is that it also works for large transactions, look at the liquidity that large nodes have.
I get the feeling that I only see excuses from groups that are not interested in making certain properties of Lightning known and discourage the user to use it.
As for example quotes the complexity, the operations I am performing are the easy ones than encrypting the wasap backup. The complexity that the protocol may have is totally isolated from the user....