Oracle staleness check present
Jupiter Perpetual Exchange's assessment for RD-F-059 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Staleness check is present — the fallback logic explicitly evaluates whether Edge is 'stale' before using it. If stale, falls back to Chainlink/Pyth. The 70% reduction in staleness events post-Edge migration (Chainwire 2024-09-12) confirms the staleness check is operational. However, the exact staleness window (seconds) is not publicly disclosed. Yellow because mechanism confirmed but threshold not public.
Sources #
- URLChaos Labs Edge Oracle — Staleness Improvement StatisticsChainwire 2024-09-12 — '70% reduction in price staleness events' post-Edge migration confirms staleness check is active and effectiveretrieved 2026-05-16
- Jupiter Perps Technical Reference — Staleness CheckJupiter technical reference — 'if the Edge oracle is not stale' — confirms staleness check in fallback selection logicretrieved 2026-05-16
Methodology #
Determine whether the protocol rejects oracle reads older than a declared maximum age (i.e., checks `updatedAt > block.timestamp - maxStaleness`).
See the full factor methodology and distribution across all protocols →