External keeper/relayer not redundant
Cap (cUSD / stcUSD)'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 #
Cap uses Gelato automation (contracts/gelato/ directory confirmed in cap-contracts repo). Gelato used for automated protocol operations (fee auction, fractional reserve management). Single keeper provider with no documented redundancy or failover to alternative automation network. Yellow because user-initiated operations remain functional even if Gelato fails, but automated rebalancing and fee distribution would halt.
Sources #
- GitHubCap contracts repo — gelato directory confirmedcap-contracts repo directory listing shows contracts/gelato/ subdirectory — Gelato automation integrationretrieved 2026-05-17
- Cap docs automation referencesdocs.cap.app/llms-full.txt: automation references; Gelato used for fractional reserve and reward distributionretrieved 2026-05-17
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 →