Quote from: BlackHatCoiner on Today at 04:21:05 PM

Quote from: Kruw on Today at 03:38:59 PM

Why not use WabiSabi instead of Whirlpool so you don't have toxic change and have no lack of privacy at all?

Repeated soundbite. I ignore.

I didn't repeat myself, this was the first time I've asked you why you would choose to create toxic change from coinjoining that causes privacy loss instead of choosing not to create toxic change from coinjoining to keep your privacy.

Quote from: BlackHatCoiner on Today at 04:21:05 PM

You do not consolidate your private coins in the the coinjoin, but after it, using a mix partner.

If you are using a second coinjoin to solve the privacy flaw of the initial Whirlpool coinjoin, then why not just perform a single coinjoin that doesn't have the initial privacy flaw so you can cut through these two transactions?

Quote from: BlackHatCoiner on Today at 04:21:05 PM

Yes, it does. Alice can normally register her bc1qalice input, and the coordinator will refuse to create a bc1qalice output. The attacker can be ignored.

If this request is ignored, then the coordinator would have to propose a 5 input 4 output transaction to the participants. Would you sign this transaction?

Quote from: BlackHatCoiner on Today at 04:21:05 PM

I said:

Quote from: BlackHatCoiner on Today at 01:28:49 PM

WabiSabi coinjoins literally have identifiable input and output merges

That does not mean I can de-anonymize the outputs with certainty, as I can with a 20 inputs 1 output transaction. I can only say for sure that there is information which can reduce the uncertainty, and which does not appear in Whirlpool. See yourself: https://kycp.org/#/323df21f0b0756f98336437aa3d2fb87e02b59f1946b714a7b09df04d429dec2.

That's what I'm asking - I want to see this information that reduces the uncertainty for myself. Using this coinjoin transaction, what information is revealed from these input and output merges that reduces the uncertainty?

Quote from: BlackHatCoiner on Today at 04:21:05 PM

Probably because Samourai's implementation of Boltzmann score's computation is not optimized; I just cloned their repo, entered a Wasabi transaction, and it's still loading. WabiSabis are very big in size, not even oxt.me has worked it out (TX ENTROPY is N/A in summary). Maybe I optimize it once I find the time.

So you're saying that WabiSabi is too powerful for the Boltzmann analysis technique to handle Cool