External keeper/relayer not redundant
Kamino Lend'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 #
Pyth uses decentralized publisher set (not single keeper). Switchboard On Demand is pull model. Chainlink Data Streams pull model. Kamino maintains own Switchboard feeds as supplementary. No confirmed single-keeper dependency. Relayer redundancy for Chainlink pull not fully confirmed.
Detail #
Pyth on Solana: publishers push to price accounts; aggregation is on-chain. Not a single keeper. Switchboard On Demand: oracle nodes pull on demand. Chainlink Data Streams: pull model, external relayer. Kamino maintains its own Switchboard oracle feeds (as per Exponential.fi: 'maintaining its own oracles alongside those from other providers') — these custom feeds depend on Kamino's own updater/relayer setup, which may be less redundant than Pyth's publisher set.
Sources #
- DocsExponential.fi Kamino Lend — oracle infrastructureExponential.fi — Kamino maintains own oracles alongside external providersretrieved 2026-04-27
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 →