Historical bad-debt events
Dolomite's assessment for RD-F-067 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No documented bad debt events in the current Dolomite v2 system (Arbitrum/Ethereum/Berachain deployments launched Oct 2022 onward). Rekt database has no Dolomite entry. The March 2024 $1.8M exploit targeted a deprecated pre-2020 Ethereum legacy contract (old DolomiteMarginProtocol) via stale approval drain, NOT the current v2 system. Current v2 has not socialised losses. WLFI borrower event (April 2026, $162M outstanding) is a prospective risk, not a crystallised bad debt event. March 2026 liquidation rake (10% of liquidation penalty) builds a nascent safety buffer but is embryonic in size relative to potential exposure.
Sources #
- InternalDolomite Data Cache - Rekt Sectiondata-cache sources.rekt.incidents=[] confirming Rekt database has no Dolomite listingretrieved 2026-05-16
- CryptoBriefing: Dolomite Security Exploit $1.8MMarch 2024 exploit targeted pre-2020 deprecated contract (DolomiteMarginProtocol starting 0xe2466...) via stale approval; current v2 system unaffectedretrieved 2026-05-16
- Dolomite Risk Management - Liquidation RakeDolomite risk management docs: liquidation fee rake 10% of liquidation penalty builds safety buffer; introduced March 2026; queryable via LiquidatorProxyV6.dolomiteRake()retrieved 2026-05-16
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 →