Quiet incident registry

The registry for what happened after cross-chain bridge incidents.

Most hack databases stop at the exploit. Bridge Incident Registry tracks what happened after: pauses, recoveries, reimbursements, reopenings, migrations, and shutdowns.

4
Bridge records
4
Incident cases
12
Timeline events
16
Evidence records
Foundation

Registry primitives before registry data

The first UI components establish status, maturity, freshness, callout, and empty-state patterns before canonical JSON records are added.

active paused migrated reviewed current

Incident aftermath

Track pause, recovery, reimbursement, reopening, migration, and shutdown outcomes.

Evidence-first records

Every major claim should point back to official, archival, analytical, or journalistic evidence.

Not a safety ranking

BIR records historical incidents and outcomes. It does not recommend bridges or rank safety.