Incident response time (minutes)
Usual (USD0 / bUSD0 / USUAL)'s assessment for RD-F-085 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Last incident is now the May 27, 2025 SC exploit. The affected vault was paused automatically upon BlockSec Phalcon detection — 'within the first hour' per reporting. Automatic pause within ~60 minutes of the first exploit transaction is a strong operational response. Previously scored yellow anchored on the January 2025 governance event (14-day public blog delay). Rescored green: the May 2025 SC exploit is the most recent incident and the automatic containment within <1 hour is the operative measurement for this factor.
Sources #
- URLBinance Square — Usual Protocol pauses contract after USD0 exploitBinance Square: 'Within the first hour after the exploit, Usual Protocol clarified that no liquidity was drained and user funds were not affected. The protocol paused its smart contracts following BlockSec detection.'retrieved 2026-05-17
- Usual Blog — Sky Vault Arbitrage RecapUsual blog: 'affected vault was paused automatically' — confirms automatic pause mechanism activatedretrieved 2026-05-17
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 →