★ Oracle source = spot DEX pool (no TWAP)
Jupiter's assessment for RD-F-053 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[★ CRITICAL — GREEN] No sub-protocol uses raw spot DEX pool price as an oracle. Aggregator uses live DEX pool reserves per transaction (read-time pool state, not a price oracle pattern — no TWAP needed because no asset collateralization occurs). Perps uses Edge (off-chain aggregated price with ZK-proof delivery), Chainlink Data Streams, and Pyth — all push oracles, none are single-pool spot prices. Lend uses Pyth, Chainlink, Redstone — all established push oracles. F053 critical flag does not fire.
Sources #
- DocsJupiter Perpetuals price oraclesPerps oracle: Edge + Chainlink Data Streams + Pyth (all push oracles, not spot DEX)retrieved 2026-04-29
- Oracles — Jupiter Lend Developer DocsLend oracle: Pyth/Chainlink/Redstone — push oracles confirmedretrieved 2026-04-29
- Jupiter Routing Engines — Developer DocsAggregator routing: queries live DEX pool state per transaction; no external oracle dependency for routingretrieved 2026-04-29
Methodology #
Determine whether the primary oracle for any asset/market reads spot price from a single DEX pool without a TWAP window or secondary source.
See the full factor methodology and distribution across all protocols →