Security-Council threshold reduction (RT)
Cap (cUSD / stcUSD)'s assessment for RD-F-182 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
RD-F-182 batch-24 addition, Cat 6B. T-09 v1.1 candidate. Signal fires on: Security Council / protocol multisig threshold reduction + timelock removal + new-signer addition within <=14 days. Current state: Dev multisig (0xb8FC49402dF3ee4f8587268FB89fda4d621a8793) threshold = 3, owner_count = 5 (confirmed by Safe API in data cache, api_status: found). Cap Token Owner multisig (0x80A216738E4e49B262Deae6bEb6578Bdf164c2eA) threshold = 3, owner_count = 5 (same signers). TimelockController delay = 86400s (24h) — timelock has NOT been removed. No threshold reduction from 3/5 to 2/5 or below detected. No within-14-day combined event (threshold change + timelock removal + new signer) detected. Reference event (Drift Protocol): 3/5 → 2/5 SC + timelock removal executed 6 days before $285M DPRK exploit — this pattern is absent here. Current posture is clean.
Sources #
- InternalCap data cache — TimelockController delay 86400s (not removed).research/protocols/cap/00-data-cache.json sources.governance.timelock_delay_seconds = 86400retrieved 2026-05-17
- Taxonomy — RD-F-182 definition and Drift Protocol evidenceresearch/outputs/03-taxonomy.md §v1.1 batch-24 additions RD-F-182 (Drift Protocol comparator)retrieved 2026-05-17
- Cap data cache — Safe multisig thresholds (both Safes, threshold=3/5).research/protocols/cap/00-data-cache.json sources.safe_multisigs[0] (threshold:3, owner_count:5, api_status:found) and safe_multisigs[1] (threshold:3, owner_count:5, api_status:found)retrieved 2026-05-17
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 →