Guardian/pause-keeper distinct from upgrader
Babylon Protocol's assessment for RD-F-034 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No EVM-style pause-keeper role identified. No equivalent to EigenLayer's Pauser Multisig found for Babylon Genesis. Chain halt would require 2/3+ validator consensus (Cosmos SDK crisis module). IBC rate-limiter (V2 upgrade) provides partial circuit-breaker for cross-chain outflows (10%/24h) but is not an admin-controlled pause. The concept of a guardian role distinct from the upgrader (governance) is architecturally absent in this pure on-chain governance model.
Sources #
- DocsBabylon Genesis V2 Upgrade — IBC Rate LimitingGovernance docs — no pause role documented; IBC rate limiter describedretrieved 2026-05-04
Methodology #
Determine whether a pauser/guardian role exists and is held by an address distinct from the upgrader address.
See the full factor methodology and distribution across all protocols →