Post-exploit response score
Maple Finance's assessment for RD-F-081 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Fast public communication (same-day, Dec 5 2022). V2 deployed Dec 11 (6 days) as structural fix. Kroll engaged for recovery. No comprehensive protocol-level post-mortem with named contracts/code diffs. Depositor compensation partial. Response quality: adequate speed, inadequate transparency and compensation.
Detail #
Methodology grades response quality 1-5 on: compensation, transparency, root-cause depth, operational recovery. Maple severed ties with Orthogonal same day. V2 was released 6 days later with the early-default feature fix. Kroll hired for asset recovery. However: (1) No formal post-mortem document naming specific contracts, code diffs, or governance actions published by Maple Finance itself. (2) Depositor recovery was partial — pool cover was < $2M against ~$36M in losses; up to 80% depositor losses confirmed. (3) Root cause (borrower misrepresentation + platform's absence of early-default enforcement) was stated in media but not in a structured post-mortem. Score: yellow on balance — fast operational response and structural V2 fix, but transparency depth and compensation posture are below green standard.
Sources #
- URLMaple Finance releases version 2.0 after $36M defaultThe Block — V2 release Dec 11retrieved 2026-04-27
- M11 Credit Update on Orthogonal TradingM11 Credit Medium post — on-chain default declared Dec 13, Kroll engagementretrieved 2026-04-27
- Maple Finance severs ties with Orthogonal TradingCoinDesk — same-day announcementretrieved 2026-04-27
Methodology #
Curator-score (1–5) the most recent incident response on: compensation completeness, transparency of disclosure, root-cause analysis depth, and operational recovery speed.
See the full factor methodology and distribution across all protocols →