Upgrade multisig signer configuration (M/N)
Rocket Pool's assessment for RD-F-026 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Upgrade multisig signer config: post-Oct 2025 guardian disablement, there is no single admin EOA. pDAO governance (RPL-staked voting, square-root modifier) is the upgrade path with 1-week vote delay + 1-week upgrade delay. The oDAO (18 members, 51% quorum = 10/18) handles oracle reporting and registers approved contract addresses in RocketStorage post-pDAO-vote — this is committee governance, not a Safe-style multisig. The pDAO Security Council holds pause-only powers, also a committee not a Safe. No 1-of-1 EOA controls the protocol. The 10/18 oDAO threshold for committee-style oracle/upgrade-execution is acceptable for an 18-member committee.
Sources #
- Docs
- Protocol Development Roadmap Update — Aug/Sept/Oct 2025Rocket Pool DAO Roadmap Update Aug-Sept-Oct 2025 (Oct 24 2025): we permanently disabled the protocol DAO guardian, completing the transition to full decentralised governanceretrieved 2026-05-04
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 →