About
The structured record of crypto failure.
A source-cited archive of every major crypto collapse, hack, depeg, and regulatory action — written in the tone of a journal of record, not a trading desk.
What we publish
Each event in this archive carries five pieces of structured evidence:
- An hourly timeline of what happened, drawn from court filings, exchange announcements, on-chain records and contemporary news.
- A who-was-involved breakdown — victim, attacker, enabler, custodian — with current legal status where applicable.
- Recovery tracking. For resolved bankruptcies, the percentage of user funds returned and the schedule that produced it.
- Pattern tags. The structural conditions that made the failure possible, so the same patterns are easy to spot in living entities.
- Cross-links to related events that share an actor, an attack vector, or an outcome.
What we do not publish
- Investment advice. We do not say what to buy, sell, hold or avoid. We publish what is verifiable. You decide what it means.
- Speculation. If a claim is not backed by a citation, it is not on the page.
- Anonymous accusations. Naming an actor as attacker requires a public court filing, a sanctions listing, or formal attribution by a recognised authority.
Tone
Analyst, not advocate. The job is structured documentation, not editorial. Where outcomes are contested in court, we say so. Where attribution is disputed, we say so.
How records are written
The seed catalogue is hand-curated from primary documents — court filings, OFAC notices, exchange announcements, audit reports. New events are drafted as they unfold and updated as the public record evolves: bankruptcy court dockets, sentencing, recovery distributions all flow into the same event page over time.
Free for researchers
Every event page exposes a JSON endpoint at /api/events/<slug>. Journalists, academics and other open-source projects are welcome to use it — attribution appreciated, not required.