Oracle role per asset
Babylon Protocol's assessment for RD-F-049 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No price oracle role for any asset. BTC light client (x/btclightclient) functions as a liveness dependency — tracks Bitcoin header state for validating staking registrations. Covenant committee (6-of-9 Schnorr multisig) is a liveness dependency for unbonding. Both are liveness risks, not oracle price risks. Vigilante relay stall would block delegation updates.
Sources #
- DocsBabylon Phase-1 Launch Blog — covenant committee descriptionProfile §7: BTC light client as liveness dependency, not price oracleretrieved 2026-05-04
- Babylon x/btclightclient modulex/btclightclient module documentation — maintains BTC header chain, relies on vigilante relayersretrieved 2026-05-04
Methodology #
For each oracle, classify its role as Primary / Secondary / Fallback per asset/market.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol babylon-protocol factor RD-F-049 score yellow collected_at 2026-05-04 19:43:27