Fallback behavior on oracle failure
Jupiter Perpetual Exchange's assessment for RD-F-051 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Fallback behavior explicitly documented: if Edge is stale, fallback to comparison of Chainlink and Pyth; use most recent of those two if within threshold of each other. If two or more oracles fail simultaneously, no price update occurs — protocol halts rather than propagating a potentially bad price. This is a conservative, safe failure mode. No last-known-price propagation risk identified.
Sources #
- DocsJupiter Perps Technical Reference — Oracle Failure BehaviorJupiter technical reference — explicit statement: 'If two or more oracles fail, no price update will happen' confirming halt-over-bad-price fallback designretrieved 2026-05-16
Methodology #
Identify the declared fallback behavior (pause, secondary source, last-known-price, revert) when the primary oracle reverts or reports a stale value.
See the full factor methodology and distribution across all protocols →