Upgrade multisig signer configuration (M/N)
Chainlink CCIP's assessment for RD-F-026 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
MCMS signer count and group quorums are deliberately not disclosed by Chainlink Labs. The contract supports up to 200 signers and 32 groups with hierarchical group-based quorum (not simple M-of-N). getConfig() function exists on-chain but results are not published in documentation. Structural transparency gap acknowledged by Chainlink.
Sources #
- DocsOnchain Architecture - Upgradability (EVM) | Chainlink DocumentationCCIP upgradability docs — signer info not publicly disclosed; geographic distribution stated but no countsretrieved 2026-05-16
- ManyChainMultiSig ABI — EtherscanManyChainMultiSig ABI shows getConfig() returns groupQuorums and groupParents arrays; MAX_NUM_SIGNERS=200, NUM_GROUPS=32retrieved 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 →