Breakage analysis per dependency
Lombard Finance's assessment for RD-F-052 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Babylon failure: yield halts entirely; LBTC remains BTC-backed but earns no staking rewards; no fallback yield source documented. Bascule failure: large mints blocked (below-threshold mints still Consortium-gated). CCIP incompatibility (CCIP 1.6.0): bridge path 1 may fail silently per 'NOT TESTED AFTER UPGRADE' comment in TokenPool.sol. Chainlink staleness: downstream lending markets mis-price LBTC as collateral. CubeSigner/HSM compromise: catastrophic custody risk for $1.04B BTC. No documented mitigation for CubeSigner HSM failure. No documented graceful-degrade for CCIP 1.6.0 incompatibility. Yellow: major dependencies analyzed but mitigations incomplete for several critical dependencies.
Sources #
- DocsLombard Finance — LBTC DesignLombard protocol architecture — Babylon and CubeSigner dependenciesretrieved 2026-05-05
- Lombard CCIP TokenPool adapter sourceTokenPool.sol — NOT TESTED AFTER UPGRADE OF CCIP TO 1.6.0 commentretrieved 2026-05-05
- Cubist — Bascule DrawbridgeCubist Bascule Drawbridge — minting gate failure analysisretrieved 2026-05-05
Methodology #
Produce a short per-dependency text describing which protocol functions halt or degrade and impact severity if each declared dependency fails.
See the full factor methodology and distribution across all protocols →