Oracle staleness check present

PancakeSwap'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 #

Predictions: oracleUpdateAllowance constructor param confirms staleness mechanism intent. Docs note oracle refreshes ~every 20s; rounds cancel if oracle not updated by round end. Implementation completeness not fully verified (source truncated on BscScan). Concern: AVAX/USD (86400s heartbeat) and COMP/USD (86400s) — 24h stale price window possible for feeds with these heartbeats.

Sources #

Partner feed
00-data-cache.json oracle_feedsData cache: AVAX/USD heartbeat_seconds=86400; COMP/USD heartbeat_seconds=86400retrieved 2026-04-28
Etherscan
PancakeSwap Prediction V2BscScan PredictionV2: constructor takes _oracleAddress and _intervalSeconds; oracleUpdateAllowance storedretrieved 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 pancakeswap factor RD-F-059 score yellow collected_at 2026-04-28 19:10:57