Upgrade multisig signer configuration (M/N)
Babylon Protocol's assessment for RD-F-026 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
BABY governance: DAO model (no fixed M/N threshold; voting power = bonded BABY stake). Covenant committee (Bitcoin layer): 6-of-9 threshold, confirmed from global-params.json (covenantQuorum=6, 9 public keys). Phase-1/2 composition: AltLayer 1 key, Babylon Labs 3 keys, CoinSummer 1 key, Cubist 1 key, Informal Systems 1 key, RockX 1 key, Zellic 1 key. Babylon Labs holds 33.3% of committee keys — below 6-of-9 threshold alone but concentration notable at $4.16B TVL.
Sources #
- GitHubBabylon bbn-1 Staking Parametersbbn-1 global-params.json — covenantQuorum=6, 9 covenant public keysretrieved 2026-05-04
- Babylon Bitcoin Staking Mainnet Launch — Phase 1Phase-1 covenant committee composition (AltLayer, Babylon Labs x3, CoinSummer, Cubist, Informal Systems, RockX, Zellic)retrieved 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 →