From discussions in our beloved Meta thread
Mixers to be banned (link to first relevant post) I got an idea for a mixer business model which could be both private and almost safe to not support criminals, at least the "big ones". The initial idea was combined with an
idea by @joker_josue. Just today I refined the model a bit more based on thoughts about other posts in that thread.
This mixer concept would have 2 goals:
1) Be able to offer high privacy standards: a no-log or almost no-log (i.e. delete logs every day) policy, and no registration nor KYC checks of any kind (with the exception of cases where users don't follow the rules of the service).
2) Be able to block most coins which come from theft and other forms of crime, without having access to the coins themselves. Thus they wouldn't be forced to seize them.
The mixer or swap would have the following rules:
1) Users can mix or swap small amounts without any KYC check. "Small amount" would be really relatively small, I would set the limit at about the equivalent of $1000 per day or less, perhaps only $500.
2) The remaining users who want to mix more than $500 or $1000 per day would have to go through a pre-screening of the UTXOs they want to mix, done on a form on an
independent website operated ideally by a different party, where the UTXO is analyzed by a chain analysis algorithm but
without a deposit. If the funds are detected as high-risk, i.e. directly coming from criminal sources, they will be rejected. All other coins get a token [1] and they are allowed then to mix.
3) KYC will only enforced if the users deposit coins which break both rules, i.e. they were recognized as high risk, more than $500/$1000 and the user deposits them without having a token.
4) The pre-screening is done via a web form where the address or the UTXO can be entered, or an API. This ensures
the mixer has never access to coins which could trigger an obligation to seize them. This means: The final deposit of the coins you mix will happen only if the pre-screening has succeeded or the funds are small enough.
For rule 1 to work, there is an additional rule:
5) Funds that pretend coming from different users in a single day, cannot come from the same origin address, i.e. the users cannot simply try to identify as "different users" and split their coins open. This means that the coins being mixed in a single day by any user (without pre-screening) cannot be from the same origin.
And there is an important additional "rule" to prevent the mixer being silently collecting data:
6) The service should be Tor-only and usable without JavaScript. Above all the pre-screening "service" would only be allowed on a website with an onion address.
Example: Let's say an user has an address with 1 million USD worth of BTC. He moves them around during 72 hours and tries then to open 1000 mixing instances on the mixer. The first mixing process would go through, but from the second one all others will be rejected because the coins come all from the same origin.
There could be an exception for coins which come from old origin addresses, for example if the coins were already split 2 months ago or more. But that would normally not be a problem, as all the algorithm wants to ensure is that the same user only mixes $1000 per day without pre-screening. This would also prevent the situation that somebody has received a payment some time in the past and mixed the change coins just the same day the person who paid the coins wants to mix the change. However, for that to happen one of both users would have to have very bad luck that exactly the same day the other party would have mixed the coins

What d'you think? I think such a mixer could be what many Bitcoin users want: 100% KYC-less for small funds mixed by retailers, and still with a high chance to be relatively "safe" from law enforcement. For criminals, the mixer would be to slow to "pre-launder" the funds through them.
Of course the protocol would not be completely legal in jurisdictions where all custodial Bitcoin services are forced to do KYC, but there are several countries such a service could be still run.
A small detail:
[1] Technically, the token could be simply consist of the UTXO the user provided, signed by the certificate of the mixer or the entity operating the pre-check. This avoids that there is any direct data connection between the pre-screening instance and the mixer itself - because the mixing website would recognize the signature of the pre-screening entity, if the UTXO is the same one than the one pre-screened.