Direct answer
A crypto mixer enforcement timeline can help readers understand public case context, but it must keep source dates, case status, and claim boundaries visible. Mixer Explained summarizes official releases involving Helix, Blender.io, Tornado Cash, ChipMixer, Sinbad.io, and Bitcoin Fog without recreating mechanics or drawing personal conclusions.
Timeline
| Date | Matter | Primary source | Public status cue |
|---|---|---|---|
| 2021-08-18 | Helix | DOJ | Guilty plea public release |
| 2022-05-06 | Blender.io | Treasury | Sanctions public release |
| 2022-08-08 | Tornado Cash | Treasury | Sanctions public release |
| 2023-03-15 | ChipMixer | DOJ | Seizure and charges public release |
| 2023-11-29 | Sinbad.io | Treasury | Sanctions public release |
| 2024-03-12 | Bitcoin Fog | DOJ | Conviction public release |
How to read the timeline
Each entry should be read as a source-backed public reference. A timeline does not merge different legal statuses into one category.
What it does not prove
The timeline does not decide the status of unrelated tools, users, protocols, or jurisdictions. It shows why case status and source class matter.
Review checklist
- Is the entry source-backed?
- Is status language precise?
- Are allegations and outcomes separated?
- Are 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 - Public case context, not an operational description.
- U.S. Treasury sanctions Tornado Cash - Public sanctions context and claim-evaluation boundary.
- U.S. Treasury sanctions Sinbad.io - Public sanctions context for risk map entries.
- Justice Department seizes ChipMixer - Public case context for enforcement-pattern pages.
- Ohio resident pleads guilty to operating Helix - Public case context for legal/compliance discussion.
- Bitcoin Fog operator convicted - Public case context for enforcement timeline.