Fallback behavior on oracle failure
dYdX v4 (dYdX Chain)'s assessment for RD-F-051 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No explicit application-layer fallback oracle identified. If Slinky consensus prices fail, GetValidMedianPrices() returns invalid for affected markets. Validator Slinky config specifies 10-second price TTL. The protocol rejects price updates that fail validation rather than falling back to a secondary source. No secondary oracle system exists.
Sources #
- DocsRunning a Validator — dYdX DocsValidator docs: Slinky price TTL 10 seconds; no mention of fallback oracleretrieved 2026-05-17
- price_update_validate.go — dYdX v4-chainvalidate_market_price_updates.go: stateful price validation with no fallback oracle pathretrieved 2026-05-17
Methodology #
Identify the declared fallback behavior (pause, secondary source, last-known-price, revert) when the primary oracle reverts or reports a stale value.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol dydx-v4 factor RD-F-051 score yellow collected_at 2026-05-17 09:58:47