External keeper/relayer not redundant
SUNSwap (sun.io)'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 #
No mandatory keeper/relayer dependency identified for core AMM operations. Pool swaps are executed on-demand by users. SUN DAO Gauge reward distribution may be triggered by user claims or a keeper, but no single-keeper single-point-of-failure exists per sun-dao-contracts README. [?] Exact keeper architecture for Gauge reward distribution not fully confirmed from available source.
Sources #
- GitHubSUN DAO contracts README — keeper architecturesun-protocol/sun-dao-contracts: README — Gauge/Minter/Distribution architecture (no mandatory keeper referenced)retrieved 2026-05-17
- V4 PoolManager.sol — no keeper in swap pathsun-protocol/sunswap-v4-core: contracts/PoolManager.sol — user-initiated swap execution, no keeper in swap pathretrieved 2026-05-17
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 sunswap factor RD-F-062 score green collected_at 2026-05-17 14:37:31