External keeper/relayer not redundant
Stake DAO's assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Multiple internal keeper/automation contracts: All Might (0x0000000a3Fc396B89e4c11841B39D9dff85a5D05), All Might V2 (0x9B3C89f4bfda2b07E15A7cF45C3F092b4b3ca074), Botmarket (0xADfBFd06633eB92fc9b58b3152Fe92B0A24eB1FF), Automation (0x90569D8A1cF801709577B24dA526118f0C83Fc75). No Chainlink Automation or Gelato dependency detected (data cache layerzero.present=false; no third-party keeper listed in profile). Two All Might versions suggest version-based redundancy. Core locker operations (deposit, withdraw) are permissionless — keeper failure delays harvest automation but does not halt principal operations. Yellow: multiple internal keepers present but not independently operated; whether they are truly independent vs centrally managed ops team is unverified.
Sources #
- GitHubSDEthereum.sol keeper/automation contractspackages/address-book/src/SDEthereum.sol — All Might 0x0000000a3Fc396B89e4c11841B39D9dff85a5D05, All Might V2 0x9B3C89f4bfda2b07E15A7cF45C3F092b4b3ca074, Botmarket, Automation listedretrieved 2026-05-16
- Data cache coverage flags — no third-party keeper.research/protocols/stake-dao/00-data-cache.json — coverage_flags: no layerzero_bridge, no third-party keeper flaggedretrieved 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 →