Oracle staleness check present
Jupiter's assessment for RD-F-059 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Lend: staleness checks explicitly documented — 600 seconds for standard operations (supply/borrow/repay/withdraw), 7200 seconds for liquidations. Pyth and Redstone use Unix timestamp freshness; Chainlink uses slot-based freshness (~400ms/slot). Perps: staleness check present (Edge staleness triggers fallback to Chainlink+Pyth comparison). Exact Perps staleness window not publicly disclosed but mechanism is confirmed operational. 600s standard (10 min) is within acceptable range for Lend volatile assets on Solana.
Sources #
- DocsOracles — Jupiter Lend Developer DocsLend staleness: 600s standard / 7200s liquidations; Pyth/Redstone Unix timestamp; Chainlink slot-basedretrieved 2026-04-29
- Jupiter Perpetuals price oraclesPerps: Edge staleness triggers fallback mechanism (confirmed in oracle documentation)retrieved 2026-04-29
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 →