★ Single admin EOA
Babylon Protocol's assessment for RD-F-027 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No single EOA or private key holds unilateral chain upgrade authority. Babylon Genesis software upgrades require on-chain BABY governance vote (MsgSoftwareUpgrade). V2 upgrade (proposal Jun 12, 2025 → activation Jun 16) and V4 upgrade (Proposal #18, Nov 2025) both confirmed as governance-voted. No Cosmos SDK crisis module sudo-admin key identified. Babylon Foundation holds significant BABY supply but cannot unilaterally execute upgrades.
Sources #
- GovernanceBabylon: v4 Software Upgrade | PolkachuV4 Software Upgrade governance proposal #18 on Babylonretrieved 2026-05-04
- Governance | Babylon DocsCosmos SDK governance module — MsgSoftwareUpgrade requires on-chain voteretrieved 2026-05-04
Methodology #
Determine whether the effective upgrade/owner/rescue role is held by a single EOA (not a multisig) with no timelock on sensitive operations.
See the full factor methodology and distribution across all protocols →