Quote from: o_e_l_e_o on Today at 01:12:32 PM

So a user imports a Wasabi wallet in to Samourai, doesn't let it sync, and Samourai uses an address it thinks is empty? OMG, Samourai bad!
Samourai release a responsible disclosure addressing address reuse and the steps taken to fix it. OMG, Samourai bad!

Wasabi try to deny address reuse happens despite blockchain evidence of it happening, and just endlessly hand wave about other clients? This is fine.

Lmao. Do you want a hand moving those goalposts again? You must be getting tired. Cheesy

My goalposts remain exactly in the same spot- WabiSabi coinjoins cannot have the outputs matched to the inputs unless it belongs to the whale:

Quote from: Kruw on April 10, 2023, 02:09:47 PM

Quote from: o_e_l_e_o on April 10, 2023, 12:10:56 PM

Or just use a coinjoin implementation which is not actively coordinating with blockchain analysis, is not anti-privacy, and is not pro-censorship.

JoinMarket remains the best but also the hardest for the average user to use. So for them they can either download Samourai on mobile or Sparrow on desktop and use Whirlpool.

Whirlpool leaks an enormous amount of information about a user's wallet that WabiSabi coinjoins hides entirely: Whirlpool reveals common input ownership from consolidating inputs into tx0 and reveals non private change that can be tracked. Additionally, since you are coinjoining with users who have leaked their IP address or xpub address, it's unlikely a Whirlpool coinjoin round ever gains any anonymity at all.

WabiSabi coinjoin fix these leaks so that no two addresses are ever linked to each other, eliminating the common input ownership heuristic and "toxic" change (as long as you are not a whale with more liquidity than the rest of the round combined, obviously).

You failed to prove otherwise.