Dependency graph (protocols depended upon)
Lombard Finance's assessment for RD-F-050 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Critical external dependencies mapped: (1) Babylon Bitcoin Staking Protocol (Cosmos appchain) — sole yield source; 4 Finality Providers: Galaxy, Kiln, P2P, Figment; no redundant yield source. (2) Bascule Drawbridge 0xc750eCAC7250E0D18ecE2C7a5F130E3A765dc260 — minting gate, Cubist-operated single entity. (3) Chainlink CCIP — bridge path 1 (CCIP 1.6.0 compatibility gap). (4) LayerZero V2 OFT — bridge path 2 (paused April 2026). (5) Hyperlane Mailbox 0x964677F337d6528d659b1892D0045B8B27183fc0 — bridge path 3. (6) Symbiotic vaults — economic guarantee layer on bridge transfers. (7) RedStone — multi-chain push oracle. (8) CubeSigner HSMs (Cubist) — BTC key management for $1.04B BTC. Yellow: multiple non-redundant critical dependencies; Babylon single yield source is material; Bascule single-operator minting gate is material.
Sources #
- URLCubist — Bascule Drawbridge for Bitcoin Bridge SecurityCubist Bascule Drawbridge blog post — Cubist as single Bascule operatorretrieved 2026-05-05
- Lombard Finance — BridgingLombard bridging documentation — CCIP + Symbiotic layerretrieved 2026-05-05
- Lombard — Chainlink + Symbiotic Guarantee LayerLombard Chainlink Symbiotic cryptoeconomic guarantee layer announcementretrieved 2026-05-05
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 →