External keeper/relayer not redundant
Fluid's assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Fluid does not depend on external keepers for core lending operations (borrow/repay/liquidate are user-triggered or open liquidations). However, Fluid Lite's Strategy Handler has a Rebalancer Module that executes cross-chain capital rebalancing — this requires an operational relayer/keeper to call rebalance functions. The automation of cross-chain bridge calls (CCIP/LayerZero) through the Bridging Module implies operational dependency on whoever triggers rebalancing. Whether this is a single keeper or redundant is not confirmed in available sources. Yellow because the core protocol has no keeper dependency but Fluid Lite product does.
Sources #
- DocsFluid Lite USD Vault Guide — Rebalancer Modulelite.guides.instadapp.io — Rebalancer Module executes capital movementsretrieved 2026-04-29
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 →