Known-exploit-template selector deployed by any address
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-162 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Known-exploit-template selector-pattern deployed by any address. Applicable: yes. Current posture: no exploit-template deployments targeting Liquity's CDP/stability-pool architecture identified. Liquity's original (non-fork) design means the Compound V2 exploit template family and Aave-fork exploit templates do not apply. No reported clone-exploit attempts against Liquity's unique architecture in any public source.
Sources #
- DocsLiquity V1 General FAQLiquity is an original protocol design (not a Compound or Aave fork); confirmed in profile section 5 and Liquity documentation; no template-exploit family documented for this architectureretrieved 2026-05-16
Methodology #
Determine whether any contract has been deployed containing a function-selector pattern matching a known exploit template targeting protocols of this class.
See the full factor methodology and distribution across all protocols →