pull down to refresh

0 sats \ 4 replies \ @ek 26 Jan \ parent \ on: Phoenix Wallet Privacy TradeOffs lightning
I think Phoenix was always running a node to be self-custodial. However, to the extent of my knowledge, it doesn’t calculate the full route on your device but uses trampoline routing and I think it only uses @ACINQ’s node as the trampoline node for now (and not multiple) since the trampoline routing specs are still WIP. This would mean they know everything about your payments.
Again, not sure if that’s still the case. I’ll send them a mail to clarify here. I don’t expect them to check their SN notifications.
write
preview
44 sats \ 3 replies \ @nout 26 Jan
I wonder if there's a difference in terms of privacy while using BOLT12 in Phoenix in 3 different scenarios
  • Phoenix sending to another Phoenix BOLT12 offer code
  • Phoenix sending to a different wallet via BOLT12 offer code
  • Another wallet sending to Phoenix BOLT12 offer code
(I also wonder if there are privacy differences based on how you use the BOLT12 in Phoenix, because there are 3 formats - human readable address (the thing that looks like lightning adress), the payment code and full URI)
reply
0 sats \ 2 replies \ @ek 26 Jan
Good questions, hopefully @ACINQ will see my email and reply tomorrow during business hours
reply
10 sats \ 1 reply \ @OT 17h
Since everything is passing through their side of the channel I'd bet it's not the best privacy focused wallet.
reply
0 sats \ 0 replies \ @ek 17h
It's possible to hide the destination with trampoline routing but I think amounts would still be revealed.
You could also calculate the route on the device but that requires more resources:
This is advantageous for lightweight LN clients that aren’t able to track the full network graph because they’re often offline or run on underpowered mobile hardware.
Privacy of receiving payments in such a setup is an issue though afaict.
reply