Incident response time (minutes)
Jupiter Perpetual Exchange's assessment for RD-F-085 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No direct protocol exploit has occurred, so there is no incident-response clock to measure. The 2025-02-06 X account hack (frontend/social, $0 protocol impact per U2) saw the account recovered the same day with co-founder Meow posting via alternative channels within hours, but this is a frontend incident not a protocol exploit and does not define F085.
Sources #
- URLCryptoPotato — Jupiter Exchange Regains X AccountCryptoPotato: Jupiter Exchange regains X account following hack same day; Meow confirmed US-based IP for attackerretrieved 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 →
rubric_version v1.7.0 protocol jupiter-perps factor RD-F-085 score not_applicable collected_at 2026-05-16 01:53:11