Signer rotation recency

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

Evidence summary #

No multisig in admin chain for either version. Factor requires a multisig to evaluate signer rotation recency. V2: immutable, no governance. V3: DAO model with no fixed signer set to rotate. Not applicable.

Detail #

V2: no governance, no signers. V3: no fixed multisig signers. UNI DAO has no AddedOwner/RemovedOwner events. Proposal threshold and quorum changes would require on-chain governance proposal — no such changes detected in recent 90 days.

Sources #

Curator note
Uniswap data cacheData cache: safe_multisigs array empty; no AddedOwner/RemovedOwner events applicableretrieved 2026-05-12

Methodology #

Measure the number of months since the most recent signer-set change (add/remove signer) on the admin multisig; flag if threshold was reduced within 14 days of a timelock removal or new-signer addition.

See the full factor methodology and distribution across all protocols →

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