Breakage analysis per dependency
Jupiter'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 inferred from documented fallback logic, not from a formal Jupiter-published breakage document. Perps: single oracle failure → degraded but functional; 2-of-3 failure → position operations freeze (JLP holders bear open-position exposure). Lend: per-market freeze on staleness/confidence breach; other markets unaffected. Aggregator: single DEX failure → routes around (30+ venues). JupSOL: Sanctum failure impairs unstaking flow. Yellow because no formal breakage analysis is published by Jupiter, and Perps breakage under 2-of-3 oracle failure carries material JLP risk that lacks a published mitigation.
Sources #
- DocsOracles — Jupiter Lend Developer DocsLend market-level halt on staleness/confidence breachretrieved 2026-04-29
- Jupiter Perpetuals price oraclesPerps 2-of-3 oracle failure → no price update documentedretrieved 2026-04-29
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 →