pull down to refresh
1077 sats \ 0 replies \ @ACINQ 27 Jan \ on: Phoenix Wallet Privacy TradeOffs lightning
Hello,
- For sending:
Trampoline routing delegates route calculation to the ACINQ node, which is how it learns the amount and destination of BOLT 11 payments.
With BOLT 12 and the support of blinded routes, ACINQ doesn't learn the destination node anymore. However, only a handful of wallets support BOLT 12 at the moment.
For backwards-compatibility, we need to keep allowing paying wallets with BOLT 11 invoices, which is why we left the privacy notice as-is. Once the whole ecosystem migrates to BOLT 12, then this privacy issue will be fixed for good.
- For receiving:
ACINQ doesn't know the origin node. It knows the destination Phoenix node and the amount.
- In the case of Phoenix->Phoenix payments, ACINQ will always know the origin and destination node, and the amount, even with BOLT 12.
Finally, note that a Lightning node id is much less persistent than an on-chain address, except for routing Lightning nodes with publicly announced channels.