Dependency graph (protocols depended upon)
Babylon Protocol's assessment for RD-F-050 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
External dependencies: Bitcoin mainnet consensus (failure impossible by definition), vigilante relayer(s) for BTC header relay (permissionless — any operator can run), IBC relayer(s) for Genesis-BSN coordination (open IBC protocol), covenant committee (6-of-9 off-chain signing service). No Aave, Uniswap, Chainlink, or DeFi protocol dependencies. CosmWasm BSN contracts show no identified external protocol calls.
Sources #
- GitHubBabylon Vigilante repositoryVigilante repository — permissionless BTC header relay serviceretrieved 2026-05-04
- Babylon cosmos-bsn-contracts repositorycosmos-bsn-contracts — CosmWasm BSN integration, no external price oracle calls identifiedretrieved 2026-05-04
- Babylon BTC staking script documentationStaking script docs — BTC stays on Bitcoin, no DeFi protocol dependenciesretrieved 2026-05-04
Methodology #
List all external protocols whose failure would directly impair this protocol (LST providers, bridges, stablecoin issuers, keepers).
See the full factor methodology and distribution across all protocols →