Historical bad-debt events
dYdX v4 (dYdX Chain)'s assessment for RD-F-067 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Reframed as insurance-fund-shortfall / bad-debt events on dYdX v4 only (per pre-mark; v3 YFI $9M event excluded per U2). v4-specific record: (1) October 10, 2025 chain halt — isolated market liquidation edge case triggered a false-negative insurance-fund balance check; protocol auto-halted (~8 hours); insurance fund was well-capitalized and no actual bad debt occurred; $462K compensation approved from fund (27 affected addresses). (2) March 2025 DAO governance approved $10M USDC transfer from insurance fund to operations subDAOs (Proposal #372), reducing fund from ~$17M to ~$7M before replenishment. Fund replenished to ~$16M by Oct 2025 via liquidation fees (~$613K/month avg). No v4 bad-debt events confirmed. Yellow because: insurance fund was reduced by governance action for non-safety purposes, creating a structural adequacy risk; October 2025 halt exposed a liquidation accounting bug that could cause chain downtime (blocking liquidations) during a volatile period.
Sources #
- URLOctober 2025: dYdX Chain Incident Review & Community UpdateOctober 2025 dYdX Chain Incident Review & Community Updateretrieved 2026-05-17
- dYdX Community Approves 10M USDC Insurance Fund AllocationKuCoin news: dYdX Community Approves 10M USDC Insurance Fund Allocationretrieved 2026-05-17
- dYdX proposes $462K payout for users affected by outagedYdX $462K compensation proposalretrieved 2026-05-17
- Contract loss mechanisms on dYdX ChaindYdX contract loss mechanisms — insurance fund role in liquidations and ADLretrieved 2026-05-17
- DRC — Utilise Insurance Fund for DAO Funding — dYdX Community ForumDRC — Utilise Insurance Fund for DAO Funding (Proposal #372, March 2025)retrieved 2026-05-17
Methodology #
Count and sum (USD) the number of documented bad-debt events where the protocol socialized losses across depositors.
See the full factor methodology and distribution across all protocols →