Security-Council threshold reduction (RT)
Uniswap (v2 + v3)'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 #
V2+V3 combined structural N/A. F182 monitors Security Council multisig threshold reductions (Drift Protocol pattern: 3/5 to 2/5 + timelock removal 6 days before $285M DPRK exploit). V2 has no governance and no multisig. V3 has no Security Council multisig — governance is a full DAO (GovernorBravoDelegator + 2-day Timelock) with no fixed signer set. V3 core contracts are immutable with no admin. No threshold-reduction event is possible in V2/V3 governance architecture.
Detail #
Batch-24 taxonomy definition: 'Real-time signal: the bridge / protocol Security Council multisig executes a threshold reduction (e.g., 3/5 to 2/5), or a timelock removal, or a new-signer addition within <=14 days of either of the above.' V2 assessment: no governance, no multisig, fully immutable — signal has no trigger surface. V3 assessment: governance is a Compound Bravo DAO with no Security Council multisig. The 'signers' are UNI token holders voting via GovernorBravoDelegator. There is no fixed M/N multisig to track threshold changes on. The Timelock (0x1a9C8182C09F50C8318d769245beA52c32BE35BC) delay is set via DAO governance and cannot be changed unilaterally by any individual. The Drift Protocol analog (3/5 to 2/5 Security Council change + timelock removal by a small fixed set of key holders before a DPRK exploit) is not replicable in a full-DAO-governed system. N/A confirmed for both V2 and V3.
Sources #
- DocsTaxonomy RD-F-182 Definition — Structural N/A for UniswapTaxonomy batch-24 — RD-F-182 definition: Security Council threshold reduction (Drift Protocol pattern); Cat 6B. Profile §11 pre-marks F182 as structural N/A for immutable DEX.retrieved 2026-05-12
- GovernorBravoDelegator — Full DAO, No Security CouncilGovernorBravoDelegator 0x408ED6354d4973f66138C91495F2f2FCbd8724C3 — full DAO governance, no fixed Security Council signer setretrieved 2026-05-12
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 →