Lightning network privacy will improve. In the meantime, users of custodial lightning wallets, like Wallet of Satoshi or Strike, reveal the destination of every lightning payment they make to their custodian. With lnproxy, these users can instead generate and pay wrapped invoices to hide the destinations of their payments from their custodians.
Users that operate public lightning network nodes, reveal the identity of their node with every lightning invoice they generate. With lnproxy, users can instead generate and give out wrapped invoices to obfuscate the identity of their lightning network nodes from their transaction counterparties.
Learn more at:
https://github.com/lnproxy/lnproxy
And try it at:
https://lnproxy.org
me@lnproxy.org
->me@me.com
would mean that there's no way for the payee to confirm that nothing fishy is going on with the invoices generated forme@lnproxy.org
, since they'd be provided directly to the payer by lnproxy.me@me.com
would first access the lnproxy api to hide the@me.com
public key? Then the owner ofme.com
could trust the bridge server code they're running to make sure that the payment hashes always match and the "max fees" don't change.