External keeper/relayer not redundant
Jupiter'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 #
Jupiter Perps relies on a dedicated keeper to push oracle price updates during trade execution and on a regular schedule. The keeper architecture (single vs. redundant keepers, permissionless vs. team-operated, failover mechanisms) is not publicly documented. If the keeper fails, oracle price updates halt during the outage window, which could leave positions unable to be opened/closed/liquidated. Assessed yellow — single keeper risk cannot be ruled out from public sources. Aggregator and Lend do not have an identified external keeper dependency for oracle updates.
Sources #
- URLJupiter Perpetuals price oraclesPerps oracle updates via dedicated keeper during trade execution and regular updates — keeper redundancy not documentedretrieved 2026-04-29
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 →