External keeper/relayer not redundant
Convex 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 #
No single keeper/relayer dependency. The earmarkRewards function on Booster is permissionless — any external caller can trigger gauge CRV claiming. No Gelato, Chainlink Automation, or single-keeper dependency in Convex's core reward path. Reward claiming is open to anyone.
Sources #
- GitHubConvex Finance Platform Contracts — Booster.sol earmarkRewardsconvex-eth/platform — Booster.sol: earmarkRewards has no keeper-only modifier; callable by any external addressretrieved 2026-05-16
- Convex Finance Integration Docs — Booster (earmarkRewards permissionless)Integration docs: earmarkRewards is permissionless, callable by any address; no keeper restriction documentedretrieved 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 →
rubric_version v1.7.0 protocol convex-finance factor RD-F-062 score green collected_at 2026-05-16 02:41:28