Crypto post-mortem archive · Established 2026

What really happened, in structured form.

Crypto news writes the moment. Court filings live in PACER. On-chain forensics live on Etherscan. CryptoMortem is the place where all three converge — one structured record per incident, every claim cited, every recovery tracked through to distribution.

34
events recorded
$82.2B
user funds affected
25
resolved cases
7
ongoing

What we publish

Every claim sourced. Every event the same shape.

Rekt.news writes the post-mortem. CoinDesk writes the news. PACER holds the court filings. Wikipedia keeps a thin summary. None of them lets you do what an analyst actually needs: answer what really happened, where the money went, and how this compares to past failures of the same shape.

This archive does. One page per event. The timeline reads like a court docket. The on-chain flows link to the forensics. The recovery percentage updates as bankruptcy distributions land. Cross-links surface every event sharing an actor, attack vector, or structural failure.

Anatomy of a record

Five layers per event.

Hourly timeline

What happened, when, in source-cited steps. Pivotal moments highlighted; full chronology from first disclosure to final court ruling.

Who was involved

Victims, attackers, enablers, custodians, regulators — each entity linked, their role in the event tagged, their cumulative record viewable.

Structural failures

Each event tagged with the conditions that made it possible — no proof of reserves, oracle manipulation, stale delegation. Pattern library makes recurrence visible.

Recovery tracking

For resolved bankruptcies, the percentage of user funds returned. Updated as new distributions are confirmed by court filings.

Legal status

Verdicts, sentences, custodian assignments, ongoing proceedings. Linked to primary source filings where available.

Recent records

All events →

For journalists & researchers

Every record is also an API.

Each event page exposes a JSON endpoint at /api/events/<slug>. The full archive is at /api/events. No registration, no rate limit on reasonable use, attribution appreciated.