External keeper/relayer not redundant
Orca'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 #
Orca Whirlpools does not depend on an external keeper or relayer for core swap or liquidity operations. All operations are user-initiated on-chain transactions on Solana. No Gelato, Chainlink Automation, or equivalent keeper dependency found in the instructions directory or Cargo.toml. The update_fees_and_rewards instruction is permissionless (callable by anyone) — no single keeper dependency. Reward emissions are user-claimable; no relayer required.
Sources #
- GitHubInstructions directory listing — no keeper, automation, or relayer instructionorca-so/whirlpools — programs/whirlpool/src/instructions directory (no keeper/automation integration file)retrieved 2026-05-16
- Cargo.toml — no keeper or relayer crate dependencyorca-so/whirlpools — programs/whirlpool/Cargo.toml (no Gelato/Chainlink Automation crate)retrieved 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 →