Fallback behavior on oracle failure

Across Protocol'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 fallback oracle. If UMA OO unavailable: HubPool blocks new root bundle proposals (noActiveRequests modifier). Bridge fills continue via relayers but no reimbursements until OO restored. No secondary oracle source. No last-known-price fallback (not applicable to OO model).

Sources #

Curator note
Extracted from 03-oracle-deps.md — RD-F-051 finding; no URL cited in originalretrieved 2026-04-28

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 across-protocol factor RD-F-051 score yellow collected_at 2026-04-30 21:19:18