External keeper/relayer not redundant
Marinade Finance'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 #
YELLOW — Two material off-chain keeper dependencies: (1) update_price crank bot that submits the update_price instruction each epoch to update the stored mSOL exchange rate; (2) delegation-strategy-2 SAM pipeline (R scripts + PostgreSQL + validators-api.marinade.finance) that submits stake rebalancing instructions each epoch. Neither is documented as having a redundant fallback operator, Gelato automation, Chainlink Automation, or equivalent failsafe. Single-operator failure of either component leaves the on-chain state stale or frozen for an epoch. No documentation of multi-operator keeper infrastructure or on-chain keeper incentivization.
Sources #
- DocsMarinade Backend-Design.md — keeper bot architectureBackend-Design.md: bot processes stake account rewards and submits update_price each epoch; single bot architecture describedretrieved 2026-05-16
- Marinade delegation-strategy-2 — single pipeline architecturedelegation-strategy-2 repo: single pipeline; no redundancy or fallback documented in READMEretrieved 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 →