Fallback behavior on oracle failure
Babylon Protocol's assessment for RD-F-051 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No price oracle to fail. Liveness dependency fallbacks: vigilante relay failure requires manual spinup of new vigilante (permissionless but not automatic); IBC relay failure has IBC packet timeout (revert) but no automatic re-routing to secondary relayer documented; covenant committee quorum failure has no documented fallback — unbonding halts if fewer than 6/9 keys available. No automated protocol-level fallback for any liveness dependency.
Sources #
- DocsBabylon staking script — unbonding path requires covenant quorumStaking script docs — covenant committee co-signing is required for unbonding; no documented fallback if quorum unavailableretrieved 2026-05-04
- Babylon Vigilante repositoryVigilante README — permissionless, multiple instances can run, but no automated failover registryretrieved 2026-05-04
Methodology #
Identify the declared fallback behavior (pause, secondary source, last-known-price, revert) when the primary oracle reverts or reports a stale value.
See the full factor methodology and distribution across all protocols →