External keeper/relayer not redundant
Frax Finance'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 #
Fraxlend core operations are permissionless — borrowers and liquidators can call functions without an external keeper. Chainlink Automation is not used for core pair functions. AMO operations are triggered by the governance Comptroller (not a single keeper). Frax Oracle price updates via addRoundData can be called by whitelisted parties (not a single required keeper). No single-keeper dependency identified for core protocol functionality.
Sources #
- DocsFrax Oracle Advanced ConceptsFrax Oracle advanced concepts — addRoundData callable by whitelisted partiesretrieved 2026-05-17
- Fraxlend OverviewFraxlend Overview — permissionless liquidation and borrow architectureretrieved 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 →