Incident response time (minutes)
Beefy Finance's assessment for RD-F-085 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
For the 2020-11-03 PancakeSwap incident: response timeline is documented — PancakeSwap announcement at 13:07 UTC, Beefy vault pause at 14:04 UTC (~57 minutes), rescue contract live at 17:38 UTC (~271 minutes). For the 2024-05-15 Sonne Finance event: Beefy describes response as 'within minutes' but no exact on-chain pause transaction timestamp with minute-level precision is published in available sources. [?] Exact on-chain pause tx timestamp for Sonne vaults not confirmed. The fact that Optimism vault users suffered partial losses despite the rapid response suggests the effective response window was insufficient to fully protect all users. Yellow — fast response in both cases but incomplete documentation of the 2024 event and confirmed partial user losses despite speed.
Sources #
- URLBinance News: Beefy Finance suspends 9 Sonne Vaults (2024-05-15)Sonne Finance: Beefy response 'within minutes'; Optimism vault users suffered partial losses confirming speed was insufficient for full protectionretrieved 2026-05-16
- Beefy Finance Incident Report: CAKE+DRUGS 2020-11-032020-11-03 incident report: timestamps documented — PancakeSwap 13:07 UTC, Beefy pause 14:04 UTC, rescue 17:38 UTCretrieved 2026-05-16
Methodology #
Measure the time in minutes from the first exploit transaction to the first official team statement for the most recent incident.
See the full factor methodology and distribution across all protocols →