pull down to refresh
What about exchange to liquid to cold storage
and storage to liquid to lightning to spending?
reply
reply
Yeah I swapped my wasabi use to doing peg in and peg out on SideSwap to break the KYC exchange link. I was told this was a decent way to improve privacy because the UTXO history goes into a black box when you peg into liquid and when you peg out it’s hard to trace that history back to an exchange
Liquid is custodial but it's a federation not one entity
reply
There's no such thing as a federation, that's a marketing stunt. Still one API surface point of failure, and even if there are N keys there's no way to prove how they are actually distributed.
Great question. It requires a very nuanced answer.
It depends. A small coinjoin tx will have a smaller anon set, just like a smaller routing node on Lightning. Ultimately, small coinjoiners and small routers all interlink with the big ones, so their privacy overlaps.
A Sybil attacker in a coinjoin needs to flood the round with liquidity, and somehow manage to exclude strangers from participating.
A Sybil attacker in Lightning needs to create a lot of nodes and selectively peer with targets to intercept payment routes. This is weakened somewhat if HTLCs are upgraded to PTLCs, but timing and amount analysis remains an issue. Multipath payments and rebalances help skew amount analysis though, so there's hope.
Sender privacy has always been good on Lightning. Receiver privacy requires Alias SCID, Blinded Paths/Bolt12, lnproxy, etc.
Taproot fixes this: Cooperative closes use the keypath instead of the script path. But, your concern remains if the channel is force closed instead.
Money can only flow in two directions:
For savers: Exchange -> Wasabi -> Coinjoin -> Cold storage
For spenders: Cold storage -> Wasabi -> Coinjoin -> Lightning -> Spending
You will need to learn Lightning no matter what. Coinjoin does not scale by itself, it's just how you should move around on the base layer when opening/closing channels.