External keeper/relayer not redundant
Save (formerly Solend)'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 #
No mandatory single keeper/relayer dependency identified. Pyth pull oracle (post-2024 migration): users and liquidators submit price updates with their transactions (pull model — no single keeper). Switchboard: relies on Switchboard publisher node network with multiple operators. No Gelato, Chainlink Automation, or single-keeper relayer identified in the program source or docs. Redundancy at oracle network level is assumed for Pyth (major network) and Switchboard.
Sources #
- DocsPyth Developer Hub — Pull Oracle Updatesdocs.pyth.network/price-feeds/core/pull-updates — pull oracle model, no single keeper requiredretrieved 2026-05-17
- Save Finance — Oracles documentationdocs.save.finance/protocol/oracles — feed-dependent refresh rates; no single-keeper dependency documentedretrieved 2026-05-17
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 →