External keeper/relayer not redundant
Maple 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 #
Liquidation is permissionless — any address can call liquidation functions when a loan is undercollateralized. No single keeper/relayer dependency for core liquidation path. Pool strategies (Aave/Sky) use internal protocol calls.
Detail #
Protocol docs and MapleGlobals source indicate permissionless liquidation design (institutional borrowers but liquidation is not keeper-gated). No Gelato or Chainlink Automation dependency in core liquidation path identified. AaveStrategy and SkyStrategy use direct calls, not external keeper interfaces.
Sources #
- Docs
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 →