@kruw thanks I'll ask other questions after analysing your replies. It doesn't look like zkSNACKs are keeping info which links users after mixes but it's about trusting what they're saying.
There's no trust in zkSNACKs necessary - Wasabi is completely open source so you can verify for yourself that no identifiable data is ever sent to any third parties, including coinjoin coordinators such as zkSNACKs.
Wasabi wallet being marketed as a privacy solution while simultaneously funding blockchain analysis is contradicting. I haven't seen data they're doing excessive bad things. Analysing incoming coins for
naughty status isn't the biggest crime if it's designed to stop crime. If my wallet's hacked coins were sent to any address on its way to Wasabi for mixing I'd be happy if they succeeded in stopping coinjoins so I'm not getting why that makes people upset.
Yeah, it's quite strange to see o_e_l_e_o be so passionately furious at the idea of a business refusing to make stolen money private that he would misdirect that anger at an open source project that allows anyone to run a competing business. If he hates zkSNACKs so much, why isn't he simply running his own WabiSabi coordinator by copying and pasting their open source code and making them go out of business by offering their service for free instead of charging any fees?...
Which data's being stored by zkSNACKs in this transaction if I'm using Wasabi wallet.
o_e_l_e_o sends 0.1 btc to arabspaceship123
arabspaceship123 sends 0.1 btc to Wasabi wallet
Wasabi wallet sends mixed 0.1 btc to arabspaceship123
arabspaceship123 sends 0.05 btc to o_e_l_e_o
arabspaceship123 sends 0.05 btc to theymos
The data stored by zkSNACKs is the exact same data that is stored on everyone else's full node when these transactions are confirmed in blocks. zkSNACKs has no knowledge about who owns coins that have been mixed.
In your opinion what's right to do if your wallet with 1 btc gets hacked. On blockchain you trace funds were sent to wallet bc1xx so you report it to police. A month later the coins moved to Binance. Soon your coins will be returned because they've been seized after blockchain analysis. That's happening now with exchanges so it can't be a bad process reuniting owners with stolen coins.
Scanning incoming UTXOs in Wasabi wallet it's the same as Binance or other exchanges doing it. What they're doing with data isn't clear. If it's being misused for unfair data collecting after it's completed its purpose it shouldn't be used. I don't trust any companies to voluntarily delete data after if they're able to profit from it.
It's not quite the same as an exchange because there's no way that stolen coins can be seized by a coordinator, coinjoins are non custodial. If a coordinator realizes coins are stolen, they can only refuse to include them in coinjoin transactions they coordinate.
Wasabi pay Coinfirm to investigate the output you are registering for coinjoin. So Coinfirm will absolutely be looking at the history of that output and seeing where it came from. If any of the previous addresses have ever been linked to an identity (such as via KYC, via addresses being shared publicly, via connecting to third party servers, via other transaction heuristics, etc.) then that will be identified and Coinfirm will be storing, sharing, and selling, that information on to other third parties.
This is completely wrong. Wasabi coinjoin coordinators do not have any knowledge of who coinjoin outputs belong to. You would be correct backdoors such as those in Samourai's coinjoin coordinator allow tracking the outputs that were created from coinjoin inputs due to xpub addresses and IP addresses being leaked by the Samourai or Sparrow client, but Wasabi clients automatically assume any coordinator is malicious and
never reveal ownership of coinjoin outputs to them thanks to using compact block filters and Tor by default.
They're storing the address used by Satoshi in tx1 before coinjoins but aren't storing tx details after mixing so they can't link anything between tx2-7.
Yes, this description is correct.