External keeper/relayer not redundant
crvUSD (Curve Stablecoin)'s assessment for RD-F-062 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No Chainlink Automation, Gelato, or keeper dependency for core protocol operations. price_w() on AggregatorStablePrice is called on every user interaction (borrow, repay, liquidate) — self-keening via user activity. PegKeepers are permissionless (any caller can trigger). MonetaryPolicy rate_write() called when needed. LLAMMA soft-liquidation triggered by arbitrageurs. No single-keeper dependency identified.
Sources #
- EtherscanPegKeeper v2 (USDC) — EtherscanPegKeeper v2 contract confirming permissionless update() functionretrieved 2026-05-16
- Curve Stablecoin Deep Dive — StateMindcrvUSD system design documentation confirming permissionless PegKeeper triggering and user-interaction-driven price_w() callsretrieved 2026-05-16
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 →