Direct answer_
How it works
Two risk families survive a mix, and both have public body counts. On the chain, an observer can work from amounts, timestamps, change guesses and your deposit address's earlier links — the analytics built on those signals has convicted mixer operators. In custody, the party holding your coins decides whether payout happens — and operators have been arrested, sanctioned and sentenced while user coins sat in their pools.
What it doesn't change
Service wording removes neither risk. Most of what you can still control begins after the payout.
Taint analysis: what it actually reads
Taint describes a conclusion about transactions. The underlying material is public, and some of it predates the service.
You cannot watch someone draw the conclusion, but you can inspect the public material it uses.
Exposure begins before the mix. Your deposit address's earlier history remains in the same public record, beyond the operator's reach.
An anonymity promise does not alter that record. The ledger keeps transactions.
Neither a setting nor a promise changes records that existed before the mix.
Risk register for a custodial mix: what creates each exposure, and what fails to remove it
Scroll horizontally to compare all columns_
| Risk | What creates it | What does not remove it |
|---|---|---|
| An address already connected to you | The deposit address carries a published history from before you reached the service | Mixing the coins that left it. The earlier history stays published and still points at you. |
| A guess about which output was your change | Past payments returned a remainder to you, and an observer has to work out which output that was | Anything the operator does now. The guess is about transactions published before the mix. |
| Amount matching between what went in and what came out | Both amounts sit in the public ledger where anybody can compare them | Splitting on the way out. The pieces stay public, and so does the sum they came from. |
| Timing between your deposit and your payout | Both transactions carry timestamps, so the gap between them is readable | A carefully chosen delay. The setting is a pattern in its own right, and an unusual one stands out. |
| The operator stops paying out | Custody puts control of the coins with the service for as long as the mix runs | Reassuring wording on a front end. It does not move control of the coins. |
| What the service observes about your session | The operator receives your request, and the addresses you type into it travel inside that request | Routing around the network layer. The addresses you submitted were the payload of the request. |
Address decorrelation and where it stops
Pooling and splitting can make a payout harder to identify. They do not make the record disappear.
A pool puts your payout among other people's payouts. The effect applies when an observer has to decide which output was yours.
After that, the payout lands in an address you chose and behaves like any other coins you hold. Later use can reconnect what the mix made harder to follow.
The technique only covers the gap between deposit and payout. No setting reaches past the point where you start spending.
What pooling changes
- Pooling gives an observer several candidate payouts instead of one line to follow.
What splitting adds
- Splitting multiplies the withdrawals you then have to keep apart from each other.
What reconnects the trail
- An address you use twice, or a balance you rebuild out of several withdrawals, reconnects what the mix separated.
Timing, amounts and the many-addresses pattern
Timing and amount patterns both reach the public ledger, and uniqueness can turn either into a signal.
A window nobody else chose can describe one user instead of a crowd. The same is true of a set of unusual amounts.
Several destinations create a group of withdrawals whose amounts can be added and compared with the deposit. The pieces can begin to identify one another.
No measured setting makes a timing or amount pattern safe. Address reuse and later aggregation can create new links after the payout.
Custodial risk: the service holds your coins
Chain-side risk assumes the payout arrives. Custody risk starts earlier, when someone else controls the coins — and 2024 alone produced two prison sentences for mixer operators.
If that assumption fails, there is no payout transaction. Chain-side exposure affects privacy; custody exposure can cost the coins.
Wallet settings do not change it. Delay and split options apply only if a payout happens, and the operator decides whether it does.
A copied front end creates the same exposure more cheaply: it only needs you to reach the wrong address first.
Two habits help: verify where you landed before sending, and keep the amount with a stranger within a loss you can absorb.
Operational risk outside the blockchain
A mix also creates a session with the operator, whether or not anyone reconstructs a link on chain.
Here nobody needs to infer the destination. The operator received it directly, while a ledger observer works from patterns and likelihoods.
What happens to the request later cannot be checked from outside. No-logs wording describes an intent, not a practice that an outsider can observe.
Your transactions are public; the request sent to an operator is not.
Frequently asked questions
Can a mixer make my coins untraceable?
No. Your deposit and withdrawal remain in confirmed blocks permanently. A mix can make the connection between them harder to draw, but it does not delete either entry.
What does taint mean when a service or a thread uses the word?
It names a conclusion, not something stored on your coins. Firms link addresses with heuristics and may report confidence that a group belongs to one owner. The result is a probability that can be wrong, so a taint claim describes what someone concluded rather than what the ledger recorded.
Can the operator simply keep my coins?
Custody makes it possible, and that is a structural risk rather than an accusation against any operator. The service controls the coins while the mix runs, so the risk of no payout travels with that control. When operators were taken down — Bitcoin Fog, Helix, Samourai — the coins in their systems went with them. Wallet hygiene and delay settings do not change who holds the coins.