Comparison
Tornado Cash vs a Mixer Service
One is a protocol; the other is a service. The comparison matters because they carry different claims: code behaves as written, a service behaves as it promises — and only one of those can be read before you send.
what differs
Protocol behaviour versus service policy — read both before choosing.
Tornado Cash is referenced as a protocol; its designation status is not asserted here without a bound primary document (OFAC roots checked 2026-10-31).
Side by side
Where they differ
| Dimension | Protocol | Service |
|---|---|---|
| What you rely on | Contract logic, publicly readable | The service's stated policy |
| Data kept | None by the code; chain data remains | Whatever the service says it keeps |
| Who can fail you | Code behaviour or chain conditions | Operator decisions, terms, solvency |
| Legal exposure | Same class question: who used it | Plus the service's own status |
The honest tradeoff
Readability vs convenience
A protocol shows its rules; you can read what it does. A service handles complexity — conversion, payout logic, limits — but you rely on its word for the parts it performs privately. Neither is universally better: the right choice depends on whether you can inspect what you're relying on.
The common ground: both are methods for breaking a naive one-to-one link, and both cannot make an on-chain transaction disappear.
source_state: Comparison derives from the comparison contract; no safety ranking is asserted (slice 2026-08-11 syntheses). (search slice 2026-08-11)
Choose your tradeoff
Read the legit checklist, then continue to the handoff screen for the handoff destination.