Upgrade multisig signer configuration (M/N)

Uniswap (v2 + v3)'s assessment for RD-F-026 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

V2: Immutable (display='Immutable'). V3: DAO model — no fixed signer set (display='DAO'). No Safe multisig in either governance chain. Data cache: safe_multisigs=[]. Combined: not_applicable.

Detail #

Neither V2 nor V3 uses a multisig in the primary governance chain. V2 has no governance at all. V3 governance is UNI DAO â†’ GovernorBravo â†’ Timelock — no Safe/Gnosis multisig intermediate. Data cache safe_multisigs array is empty. Proposal threshold = 2,500,000 UNI; quorum = 40,000,000 UNI.

Sources #

Etherscan
Uniswap GovernorBravoDelegatorGovernorBravoDelegator — admin chain confirms no multisigretrieved 2026-05-12
Curator note
Uniswap data cache governance sectionData cache safe_multisigs: [] — no Safe multisig detectedretrieved 2026-05-12

Methodology #

Read `threshold` and `getOwners()` on the multisig controlling upgrade / sensitive ops. Store as `required` (M) and `total` (N); render as "M/N". For EOA admins record `required=1, total=1` (display "1/1"). Null when admin is immutable or full DAO with no fixed signer set.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol uniswap factor RD-F-026 score not_applicable collected_at 2026-05-12 10:36:11