External keeper/relayer not redundant
BENQI'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 #
BENQI does not use an external keeper or relayer for core protocol operations. Liquidations in the Compound V2 fork model are permissionless — any caller can invoke liquidation on undercollateralized positions directly. No Gelato, Chainlink Automation, or custom keeper contract identified in the protocol architecture. sAVAX staking rewards accrual is managed by the protocol's own Avalanche P-Chain interaction, not an external keeper.
Sources #
- DocsBENQI Core Markets ContractsBENQI core contracts page — no keeper contract listedretrieved 2026-05-16
- Compound V2 DocumentationCompound V2 liquidation model — permissionless liquidation by any callerretrieved 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 →