BlackHatCoiner, you still haven't followed up on our original conversation about me tracing Whirlpool users:
BlackHatCoiner, you merited a post above but you haven't responded to your previous conversation:
Look. I agree you believe you educate people about Bitcoin privacy, but we have repeated this conversation around solutions for privacy quite a lot of times. The fact that you still quote these whirlpool messages, as if they even mean something substantial, shows with what tenacity you're trying to sabotage Samourai.
What do you mean "as if they even mean something substantial"? These Whirlpool addresses are linked to each other.
What's dust? Gimme my 5000 sat that costed more than double that amount to be created!
Your math is wrong:
At 37.5 sats/vbyte, it costs 1163 sats to create a segwitv0 output (31 vbytes) and 1612.5 sats to create a Taproot output (43 vbytes). Smart clients make sure to choose outputs that aren't dust:
https://github.com/zkSNACKs/WalletWasabi/issues/10675However,
Whirlpool clients create traceable dust that does cost more than their value to create. I reported this to Samourai, but the bug report was deleted without comment:
https://web.archive.org/web/20231025112756/https://code.samourai.io/wallet/samourai-wallet-android/-/issues/461Oh! It's supposed to confuse the observers of the coinjoin, that explains everything! Let's start reusing addresses in both inputs and outputs then, as in
Wasabi 1.0. That will definitely help, because we will confuse chain analysis even more. Why kind of a clown service reuses addresses in both sides in the first place? That will leave them so speechless that they will give up!
The service does not choose the addresses, users choose their own addresses.