External keeper/relayer not redundant
Aerodrome 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 #
Aerodrome core operations are permissionless. Epoch-boundary operations (Minter.updatePeriod, Voter.distribute) are callable by any external address — not gated to a single keeper/relayer. The protocol does not use Gelato, Chainlink Automation, or any proprietary keeper service for core functions. No single keeper failure can halt swaps or withdrawals.
Sources #
- GitHubAerodrome Minter.sol — permissionless keeper patternaerodrome-finance/contracts Minter.sol — updatePeriod() callable by anyone; Voter.sol distribute() callable permissionlesslyretrieved 2026-05-04
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 aerodrome factor RD-F-062 score green collected_at 2026-05-04 19:56:03