Security-Council threshold reduction (RT)
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-182 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Security-Council threshold reduction real-time signal (batch-24 addition, Cat 6B). Not applicable: Liquity has no Security Council, no multisig admin controlling core contracts, no timelock on core contracts. The v2 Governance contract 0x807def5e7d057df05c796f4bc75c3fe82bd6eee1 is a PIL-direction contract only with no upgrade or pause authority over core contracts. The Bounties Safe 0xf06016d822943c42e3cb7fc3a6a3b1889c1045f8 holds bounty funds only (not a protocol admin). No threshold-reduction event is possible in this immutable architecture.
Sources #
- GitHubLiquity v2 mainnet contract addressesAll Liquity v2 core contracts (CollateralRegistry, BorrowerOperations, TroveManager, StabilityPool, PriceFeed, ActivePool) listed in bold/contracts/addresses/1.json with no proxy and no admin keyretrieved 2026-05-16
Methodology #
Detect in real-time whether the bridge/protocol Security Council multisig executes a threshold reduction (e.g. 3/5 → 2/5), timelock removal, or new-signer addition within ≤14 days of either of those events.
See the full factor methodology and distribution across all protocols →