Oracle staleness check present
Across Protocol's assessment for RD-F-059 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Not applicable in price-oracle sense. UMA OO has `challengePeriodEndTimestamp` as a temporal gate (~2h liveness), not a staleness check. No `updatedAt > now - X` pattern exists because UMA OO is assertion-based, not price-feed-based.
Sources #
- Curator noteExtracted from 03-oracle-deps.md — RD-F-059 finding; no URL cited in originalretrieved 2026-04-28
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 →
rubric_version v1.7.0 protocol across-protocol factor RD-F-059 score yellow collected_at 2026-04-30 21:19:18