Wasabi's architecture was so flawed that some 133 users have been arrested after using it and chain analysis companies advertised Wasabi de-mixing services.
Two of the most horrendous issues were systemic address reuse where change addresses were later used again for mix outputs; and symmetric address reuse where the same address would show up on the input and output sides of a CoinJoin transaction. Neither of these issues were resolved with Wasabi 2.0 (Sabi Wabi or whatever they called it) and you can still find these issues occurring in Wasabi CoinJoins today.
If you want to go down this rabbit hole, here is a good place to start: https://pastebin.com/NHDVC03U
As for the new Ashigaru Whirlpool coordinator being able to link inputs and outputs, despite the unhinged takes flying around from NothingMuch and FloppyDic, the claims don't make sense IMO given the description of how the protocol works. If either of those guys have a valid point, it is getting lost due to their poor communication skills and inability to demonstrate or explain the exact issue in laymen's terms. I have seen zero evidence that a ZeroLink coordinator like the one Asgigaru is running has ever linked inputs to outputs.
Here's an example of a moron who has no fucking clue about privacy and is also a liar.
The arrests of Wasabi 1.0 were due to massive consolidations after the mix; the same would have happened with Whirlpool.
I audited the Whirlpool code myself before becoming Ashigaru and discovered the Tor vulnerability that they have now admitted.
What lessons are you here to teach? You sold Whirlpool as Zerolink, but it never was.
No replies yet.
