Emergency-veto multisig present
Babylon Protocol's assessment for RD-F-040 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Cosmos SDK governance has NoWithVeto — if ≥33.4% of voting power votes NoWithVeto, proposal is rejected and deposit burned. This is an embedded veto mechanism within the voting period. However, there is no separate veto-only multisig entity. Effective veto requires organizing 33.4% of bonded BABY within 3 days. Foundation + investors hold ~66.5% of total supply; with first cliff passed (April 2026), insider concentration could theoretically pass or veto any proposal. Community veto depends on insider non-participation.
Sources #
- Docs
Methodology #
Determine whether an emergency-veto or guardian multisig exists with power to cancel malicious proposals before execution.
See the full factor methodology and distribution across all protocols →