External keeper/relayer not redundant
Lombard Finance's assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Bascule DEPOSIT_REPORTER is a single Cubist-operated role with no documented failover keeper — if Cubist's infrastructure fails, large LBTC mints are blocked. Babylon Finality Providers are 4 entities (Galaxy, Kiln, P2P, Figment) providing some redundancy for yield continuity. CCIP relayers are Chainlink multi-node infrastructure (adequate redundancy). LayerZero routes are paused. Hyperlane relayers: not independently enumerated; Hyperlane uses multiple validators. Yellow: Bascule single-operator (Cubist) is the material keeper-redundancy gap.
Sources #
- GitHub
- Lombard Finance — Bridging ArchitectureLombard bridging architecture — CCIP redundancyretrieved 2026-05-05
- Cubist — Bascule DrawbridgeCubist Bascule Drawbridge — Cubist as sole DEPOSIT_REPORTER operatorretrieved 2026-05-05
Methodology #
Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.
See the full factor methodology and distribution across all protocols →