Canonical registry statistics

Stats

A deterministic snapshot of BIR canonical records. These figures describe the registry and its evidence coverage; they are not bridge safety rankings or market-wide estimates.

Registry snapshot

82
Bridge records
64
Incident cases
273
Timeline events
440
Evidence records
63
Major incidents
52
Unresolved incidents
Recorded canonical amounts

Loss coverage

$3,227,590,486

Sum of canonical numeric reported_loss_usd values for 43 of 64 incidents (67.2% coverage).

This total does not infer missing values, resolve conflicting claims, or claim to represent every bridge loss.

Outcome coverage

Reimbursement history

32

Incidents with an explicit reimbursement status of announced, in progress, completed, partial, or denied in the canonical incident record.

Outcome, vector, and chain breakdowns

Recovery status

Canonical incident recovery_status values. 64 canonical incidents are used as the share denominator.

Recovery status incident distribution
ValueIncidentsShare
Unknown2539.1%
Partial Recovery1625.0%
None914.1%
None Confirmed46.3%
Full Recovery23.1%
Not Required23.1%
Whitehat Recovery23.1%
Funds Protected11.6%
Not Applicable11.6%
Partial11.6%
Partial Freeze And Burn Plan11.6%

Reimbursement status

Canonical incident reimbursement_status values. 64 canonical incidents are used as the share denominator.

Reimbursement status incident distribution
ValueIncidentsShare
Unknown2234.4%
Announced1218.8%
In Progress1117.2%
Completed914.1%
Not Applicable710.9%
Not Announced23.1%
Not Required11.6%

Attack vectors

Canonical attack_vector_category values. 64 canonical incidents are used as the share denominator.

Attack vectors incident distribution
ValueIncidentsShare
Message Verification Failure1421.9%
Smart Contract Bug914.1%
Unknown812.5%
Cross Chain Contract Exploit710.9%
Validator Key Compromise69.4%
Private Key Compromise46.3%
Operator Or Governance Issue34.7%
Contract Ownership Misconfiguration23.1%
Fabricated Light Client Block23.1%
Liquidity Or Accounting Failure23.1%
Configuration Error11.6%
Event Log Parsing Bug11.6%
Frontend Or Dns Compromise11.6%
Metapool Exchange Amount Calculation Bug11.6%
Metapool Virtual Price Bug11.6%
Privileged Operator Contract Access11.6%
Relayer Or Oracle Issue11.6%

Affected chains

Incident appearances by affected chain; one incident may count toward multiple chains. 64 canonical incidents are used as the share denominator.

Affected chains incident distribution
ValueIncidentsShare
Ethereum4875.0%
Bnb Chain2539.1%
Unknown2437.5%
Arbitrum69.4%
Avalanche69.4%
Base34.7%
Bitcoin34.7%
Thorchain34.7%
Fantom23.1%
Near23.1%
Polygon23.1%
Ronin23.1%
Solana23.1%
Verus23.1%
Axelar11.6%
Bnb Beacon Chain11.6%
Cardano11.6%
Commons Chain11.6%
Harmony11.6%
Mantle11.6%
Meter11.6%
Metis11.6%
Nerve Network11.6%
Oraichain11.6%
Orbit Chain11.6%
Secret Network11.6%
Syscoin Nevm11.6%
Syscoin Utxo11.6%
Tac11.6%
Taiko11.6%
Ton11.6%
Tx11.6%
Venom11.6%
Xrpl11.6%
Recorded lifecycle chronology

First later recorded lifecycle event

Days from the incident date to the earliest linked canonical event on a later date. Same-day events are excluded; this is a record-timeline measure, not a claim about the operator's first real-world response. 64 canonical incidents are used as the share denominator.

First later recorded lifecycle event timing distribution
TimingIncidentsShare
1 day1625.0%
2–7 days1625.0%
8–30 days710.9%
31–90 days46.3%
91+ days23.1%
No later recorded event1929.7%

Data quality

74.1%
Primary evidence · 326/440
79.3%
Tier 1 evidence · 349/440
34.3%
Archived evidence · 151/440
1
Incidents without primary evidence
64
Incidents with known unknowns
9
Incidents with conflicting claims

Latest canonical verification date: 2026-09-11. Definitions and evidence rules are documented in Methodology.