External keeper/relayer not redundant
Spiko'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 #
Spiko's NAV publishing relies on an internal oracle-operator relayer as primary publisher. Chainlink Labs provides a secondary publishing path (redundancy). However no automated failover between the two is documented. If Spiko's internal relayer fails, Chainlink Labs must independently detect and fill the gap. Weekend/holiday gaps are known (business-day-only NAV). Not a traditional keeper/automation network.
Sources #
- URLSpiko Smart Contracts — Spiko Tech Blogtech.spiko.io/posts/spiko-smart-contracts/ — describes dual publishers but no failover automation: 'Spiko internal oracle-operator relayer' and 'Chainlink through their recent partnership'retrieved 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 →