★ Immutable oracle address
Babylon Protocol's assessment for RD-F-180 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Structurally inapplicable. Babylon's core protocol has NO oracle address — immutable, hardcoded, or otherwise — because it consumes no external price feed whatsoever. Data cache confirms oracle: null, oracle_feeds: []. x/btcstaking, x/finality, x/btclightclient import no oracle interfaces. CosmWasm BSN contracts show no identified oracle imports. This is the canonical 'zero oracle surface' N/A case for F180 — distinct from Wormhole (peripheral oracle not in critical path) and Hyperliquid (RED closed-source binary oracle). NOTE FOR T-14: F180 not_applicable (no oracle at all) — does not contribute to ★ critical red count.
Sources #
- GitHub
- Babylon Genesis chain — zero oracle surface confirmationData cache oracle: null, oracle_feeds: []; profile §7 explicitly states no external oracle. F180 N/A — zero oracle surface.retrieved 2026-05-04
Methodology #
Determine whether any collateral oracle address is marked `immutable` in protocol config with no admin-replaceable adapter wrapper, preventing the protocol from repricing when the upstream asset depegs.
See the full factor methodology and distribution across all protocols →