Fallback behavior on oracle failure

Orca's assessment for RD-F-051 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

No oracle is consumed, so fallback behavior on oracle failure is not applicable. The factor presupposes a primary oracle that can fail or go stale. Orca Whirlpools pricing derives entirely from pool reserves (always available while the Solana network is live). The protocol cannot experience an oracle failure.

Sources #

Internal
Data cache oracle_feeds array empty — pipeline-verified 2026-05-16T02:14:01Z00-data-cache.json sources.oracle_feeds = []retrieved 2026-05-16
GitHub
State directory — oracle.rs is internal adaptive-fee tracker; no external oracle to fall back fromorca-so/whirlpools — programs/whirlpool/src/state/oracle.rs (internal only, no external feed)retrieved 2026-05-16

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 orca factor RD-F-051 score not_applicable collected_at 2026-05-16 02:39:16