External keeper/relayer not redundant
Rocket Pool's assessment for RD-F-062 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Rocket Pool does not depend on a keeper or relayer for core protocol functionality. The oDAO committee members independently operate trusted nodes that submit transactions via submitBalances() and submitPrices() — this is a multi-party committee submission pattern, not a single-keeper dependency. No Gelato, Chainlink Automation, or custom keeper interface exists in core contracts.
Sources #
- GitHubRocketNetworkBalances.sol sourceRocketNetworkBalances.sol submitBalances(): callable by any onlyTrustedNode member; no keeper interface or dependencyretrieved 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 →