External keeper/relayer not redundant

Compound V3 (Comet)'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 #

Liquidations are fully permissionless (any address can call absorb()). No single-keeper dependency. Governance relay uses canonical bridges, not a protocol-specific keeper. COMP rewards distribution is also permissionless.

Detail #

Comet.sol absorb() is callable by any address with no access control — permissionless liquidation. No Gelato, Chainlink Automation, or similar keeper dependency for core protocol functions.

Sources #

Docs
Compound V3 docs — permissionless liquidationCompound V3 liquidation modelretrieved 2026-04-27

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 →

rubric_version v1.7.0 protocol compound-v3 factor RD-F-062 score green collected_at 2026-04-28 00:20:50