Security-Council threshold reduction (RT)
Curve Finance'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 from batch-24 (Cat 6B): Security-Council threshold reduction event RT signal. Applicable signal for Curve's eDAO Safe (0x467947EE34aF926cF1DCac093870f613C96B1E0c). Signal fires on: threshold reduction (e.g., 5/9 → 4/9), timelock removal, or new-signer addition within ≤14 days of either. Current posture: eDAO Safe threshold is 5-of-9 (confirmed in data cache: threshold: 5, owner_count: 9). No threshold reduction or timelock removal event identified in available public data. Etherscan shows most recent Exec Transaction was approximately 7 days prior to assessment date — a normal operational action, not a structural change. Aragon voting period (7-day equivalent) not shortened per available data. Signal is v1.1 candidate pending T-09 FP-rate review. Current posture: no fire condition.
Sources #
- InternalCurve Finance Data Cache — Safe Multisig Threshold00-data-cache.json safe_multisigs — threshold: 5, owner_count: 9, stableretrieved 2026-04-28
- Curve: eDAO Safe — Etherscan0x467947EE34aF926cF1DCac093870f613C96B1E0c — Safe 1.1.1 proxy, last exec approximately 7 days ago, no threshold changeretrieved 2026-04-28
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 →