Security-Council threshold reduction (RT)
Jupiter'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 #
Security-Council threshold reduction signal. Jupiter does not have a named Security Council. Admin controls are 4-of-7 Team Cold Multisig and 4-of-7 Community Cold Multisig. DAO governance pause (June 2025) is an institutional/voluntary decision — not an on-chain cryptographic threshold reduction event. No publicly documented multisig threshold change for Jupiter program upgrade authority. Drift Protocol comparator (SC 3/5→2/5 + timelock removal, 6 days pre-$285M exploit) pattern NOT detected for Jupiter. Signal not firing.
Sources #
- InternalTaxonomy Cat 6B — RD-F-182 batch-24Taxonomy RD-F-182 definition: SC threshold reduction or timelock removal within ≤14 days of anotherretrieved 2026-04-29
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 →