Oracle staleness check present

Chainlink CCIP'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 #

Oracle staleness check explicitly absent on FeeQuoter AggregatorV3 fallback - deliberate design: 'data feed staleness is unchecked in the FeeQuoter to decouple it from data feed delay issues' (FeeQuoter.sol code comment). Stale prices accepted without revert. Impact: fee accuracy risk only, not fund security. No updatedAt comparison against staleness threshold.

Sources #

GitHub
Chainlink CCIP FeeQuoter.sol - staleness check absent (deliberate)FeeQuoter.sol - explicit code comment confirming staleness unchecked; _getTokenPriceFromDataFeed calls latestRoundData() without updatedAt validationretrieved 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 chainlink-ccip factor RD-F-059 score yellow collected_at 2026-05-16 01:55:09