Phoenix for example does not route, there's not even code to route. It just gives the invoice to pay to the server that creates the route.

Yes, you could have magically switched it without changing the keys for a routing node, after you created a channel with the LSP using their API, but I guess the probability that it did not happen is 100% and Phoenix server can be pretty sure it's talking to either Phoenix wallet or phoenixd and thus see all the invoices and infer who is both the sender and the receipient.

Reply to this note

Please Login to reply.

Discussion

Sure, build it.

Problem is there are thousands of channels open by Phoenix, which can't route, they will probably not live swap their non routing wallet to your blinder and the assumption would still hold for 99.999% of payments. More than 30% is already bad privacy.

> Problem is there are thousands of channels open by Phoenix, which can't route

They can

> they will probably not live swap their non routing wallet to your blinder

There's no way to tell if they do or don't. The fact that it's possible for them to route undetectably means any of them might be doing it. Acinq has no way to know.

The assumption they can't is correct in 99.99% cases. More than 30% is already a privacy problem.

It's called heuristics.