Upgrade multisig signer configuration (M/N)
Liquity V1 + V2 (LUSD / BOLD)'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 #
No upgrade multisig exists for any core protocol contract. The only Safe (0xf06016d822943c42e3cb7fc3a6a3b1889c1045f8) is a bounty-fund management safe with no protocol-admin authority. No M/N applicable.
Sources #
- DocsLiquity v2 FAQ — GeneralLiquity v2 docs confirm no admin multisig for core contractsretrieved 2026-05-16
- Liquity Bounties Safe — EtherscanBounties Safe 0xf06016d822943c42e3cb7fc3a6a3b1889c1045f8 — Gnosis Safe holding bounty funds only, no protocol-admin authorityretrieved 2026-05-16
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 liquity factor RD-F-026 score not_applicable collected_at 2026-05-16 10:35:50