Bridge rate-limiter / chain-pause as positive mitigant
Babylon Protocol's assessment for RD-F-185 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
POSITIVE FINDING: V2 upgrade (June 2025) added IBC rate limiting capping BABY token exits at 10% of native supply within 24 hours — explicit outflow rate-limiter. No admin-triggered chain-level pause mechanism identified (Cosmos SDK x/crisis is validator-consensus-based halt, not admin key). Score yellow: rate-limiter present (positive) but no admin-triggered chain-pause capability separate from consensus. The rate-limiter is a material security mitigant for cross-chain outflow risk.
Sources #
- URLBabylon Genesis V2 Upgrade — IBC Rate LimitingV2 upgrade added IBC rate limiting: 10% of native supply per 24hretrieved 2026-05-04
Methodology #
Determine whether the bridge implements a per-window outflow rate-limiter (and at what cap), and whether the protocol team can trigger a chain-level or validator-set emergency pause.
See the full factor methodology and distribution across all protocols →