Oracle staleness check present
Orca's assessment for RD-F-059 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No external oracle is read; there is no updatedAt field to check for staleness. Factor presupposes an oracle read with a timestamp that can become stale. Inapplicable for a pure on-chain AMM.
Sources #
- InternalData cache oracle_feeds array empty — pipeline-verified 2026-05-16T02:14:01Z00-data-cache.json sources.oracle_feeds = []retrieved 2026-05-16
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 orca factor RD-F-059 score not_applicable collected_at 2026-05-16 02:39:16