Breakage analysis per dependency
Jupiter Perpetual Exchange's assessment for RD-F-052 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Breakage analysis completed for primary dependencies: (a) Edge/Doves offline → fallback to CL+Pyth; if both also stale → halt (no fund loss, but liquidations and new positions frozen during market stress). (b) Chainlink fail → Edge+Pyth still operational, minimal degradation. (c) Pyth fail → Edge+Chainlink still operational, minimal degradation. (d) All-three-stale (tail risk) → freeze at last mark price; liquidations cannot execute. (e) Chaos Labs keeper compromised → manipulated signed prices; cross-validation threshold is defence but exact threshold not public. Yellow because breakage analysis relies on documented oracle logic; actual staleness threshold and deviation bounds are not publicly confirmed, making precise timing of halt scenarios uncertain.
Sources #
- DocsJupiter Perps Technical Reference — Breakage Analysis BasisJupiter technical reference — oracle selection logic provides basis for breakage analysisretrieved 2026-05-16
- Chaos Labs Partners with Jupiter ProtocolChaos Labs partnership announcement — risk platform context for monitoring oracle performanceretrieved 2026-05-16
Methodology #
Produce a short per-dependency text describing which protocol functions halt or degrade and impact severity if each declared dependency fails.
See the full factor methodology and distribution across all protocols →