External keeper/relayer not redundant
Beefy 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 #
Beefy strategies include a keeper address for harvest/panic but harvest is functionally permissionless — anyone can call harvest() in many strategy implementations. Dev multisig can also panic vaults. StrategyFactory configures keeper as a single address but the system does not halt if keeper is unavailable; permissionless harvest prevents single-keeper dependency. The panic() fallback (withdraws from farm to strategy) provides emergency redundancy even if keeper fails.
Sources #
- DocsBeefy SAFU Practices — keeper and panic mechanismSAFU practices: panic function available as emergency fallback; keeper has panic authorityretrieved 2026-05-16
- StrategyFactory.sol — keeper role and harvest accessStrategyFactory.sol — keeper address configurable; harvest permissible by keeper or strategy-defined callersretrieved 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 →