13 sats \ 9 replies \ @sommerfeld 28 Nov 2022 \ on: Wasabi + HW Wallet Privacy Setup bitcoin
My advice is to stop using wasabi. They actively collaborate with chain analysis companies who managed to demix their coinjoins in the past.
Alternatives: whirlpools using samourai / sparrow.
You should also avoid kyc exchanges even if you coinjoin. They essentially still get the data of how much bitcoin you bought in total.
Protect yourself both from the earning and the spending side.
Can you share some more info about wasabi sharing data?
reply
From the horse's mouth: https://blog.wasabiwallet.io/zksnacks-blacklisting-update/
There are also a bunch of PDFs circulating around but I'm on my phone rn.
reply
Very interesting. It perfect the enemy of good though? I have never heard these criticisms of Wasabi before. I did find the coinjoins a bit slow and am happy to try something else. Is there a good robust single wallet solution for coin-joining and managing a HW?
reply
Being potentially state captured is far from good, nevermind captured.
Is there a good robust single wallet solution for coin-joining and managing a HW?
Sparrow (desktop-only)
Imo you should not manage a hw on a phone anyway. You should only use the hw for spending which should be rare. For receiving and tracking your savings, use the hw xpub to create a watch-only wallet in any bitcoin wallet app (e.g. bluewallet).
reply
Yes I would not imagine managing via phone, just HW watch only.
reply
Are whirlpools and coinjoins different concepts / functions?
reply
Whirlpool is a mixing tech that coordinates trustless coinjoins.
It is currently implemented in sparrow and samurai wallets.
An alternative to Whirlpool is Joinmarket which is fully decentralized but as a result, it has lower liquidity and thus a lower anonymity set. It required a bit more experience and technical background to set it up.
reply
Also, I think I can run my own node with wasabi, does that counter their analysis?
reply
The analysis is on-chain. Running your own node only gives you network-level privacy, not on-chain privacy.
reply