Direct answer
Enforcement cases help explain why mixer-related topics require careful language. Official sources record different event classes: sanctions designation or delisting, charge, plea, conviction, sentence, judgment, and forfeiture. The case register below keeps those statuses separate and does not turn them into usage documentation or a universal legal rule.
What it means
Case context is useful for understanding public risk categories and enforcement posture. It is not a substitute for the underlying legal record, and it should keep allegations, sanctions actions, convictions, and pleas distinct.
Timeline pattern
| Example | Source | Public status | Boundary |
|---|---|---|---|
| Helix | DOJ / IRS | Plea, sentence, and later forfeiture are separate events | Keep procedural status and date visible |
| Bitcoin Fog | DOJ | Conviction and sentence reported in separate releases | Do not infer appeal or forfeiture status |
| ChipMixer | DOJ | Seizure and charges; no conviction claimed here | Do not describe service mechanics |
| Blender.io | Treasury / DOJ | Historical designation plus later alleged-operator charges | Do not infer current SDN status |
| Tornado Cash | Treasury / DOJ | Historical designation, later delisting, separate charges, and a later identified conviction event | Keep sanctions and criminal case statuses separate |
| Sinbad.io | Treasury / DOJ | Designation context plus later alleged-operator charges | Avoid operational detail and personal conclusions |
What it does not prove
A case example does not prove that every privacy technology is unlawful, that every user has the same intent, or that every jurisdiction treats the issue identically.
Evaluation checklist
- Is the case status clear?
- Is the source official?
- Are allegations separated from convictions?
- Are operational mechanics omitted?
Source notes
These sources support public context and terminology. They do not turn this page into legal, financial, sanctions, or compliance advice.
- U.S. Treasury sanctions Blender.io - Historical May 6, 2022 designation context; current list status must be checked in current OFAC records.
- U.S. Treasury sanctions Tornado Cash - Historical August 8, 2022 designation context; it must be read with the later Treasury delisting release.
- U.S. Treasury: Tornado Cash Delisting - Treasury's March 21, 2025 release states that the economic sanctions against Tornado Cash were removed.
- U.S. Treasury sanctions Sinbad.io - Historical November 29, 2023 designation context; current list status requires a dated OFAC list check.
- Justice Department seizes ChipMixer - March 15, 2023 takedown and charge context; charges are allegations, not a conviction.
- DOJ charges alleged operators of Blender.io and Sinbad.io - Later criminal-charge context involving alleged operators; allegations and historical sanctions actions remain separate statuses.
- DOJ charges Tornado Cash founders - DOJ announced charges on August 23, 2023; charges are allegations unless proved in court.
- DOJ reports a Tornado Cash founder conviction event - DOJ announced the identified conviction event on August 6, 2025.
- Ohio resident pleads guilty to operating Helix - August 18, 2021 guilty-plea context; later sentencing and forfeiture are separate official events.
- Operator of Helix sentenced - November 15, 2024 sentencing context, distinct from the earlier guilty plea and later asset forfeiture.
- Government forfeits assets tied to Helix - January 2026 forfeiture context reporting legal title to more than $400 million in tied assets.
- Bitcoin Fog operator convicted - March 2024 conviction context; it must be read with the later sentencing release.
- Bitcoin Fog operator sentenced - November 8, 2024 sentencing context: 12 years and six months, separate from conviction and any later appeal or forfeiture record.