Oracle staleness check present
Wormhole's assessment for RD-F-059 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Oracle staleness check (`updatedAt > now - X`) | No Chainlink `latestRoundData()` staleness check needed in core path — no price feed consumed. For peripheral Chainlink feeds: staleness check status of individual consumer contracts not verified (those contracts are not the audited core bridge). Gap flagged. | Messages.sol: no staleness check (no price feed); peripheral contract sources not inspected | YELLOW
Sources #
- Curator noteExtracted from 03-oracle-deps.md — RD-F-059; no URL citedretrieved 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 →