Avg attacker reconnaissance time for peer-class protocols
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-163 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Attacker wallet reconnaissance time before strike (days, for similar class) — reference/analytic signal. For CDP protocols similar to Liquity: USPD-class reconnaissance is typically 30-78 days per T-01 methodology. Current posture: no reconnaissance pattern indicators identified for Liquity. Zero protocol-layer attacks in 61-month v1 history. No wallets identified as conducting reconnaissance-style pre-strike activity against Liquity contracts. Immutable architecture means even successful reconnaissance would not identify admin-key-abuse vectors.
Sources #
- Internal00-data-cache.json rektData cache rekt.incidents: []; zero exploits in 61-month history; immutable architecture reduces social-engineering attack surfaceretrieved 2026-05-16
Methodology #
Report the average number of days of attacker reconnaissance activity before a strike on peer-class protocols (lending/DEX/bridge/perps), sourced from the hack database.
See the full factor methodology and distribution across all protocols →