Oracle staleness check present
Stargate Finance'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 | RED FINDING. FeeLibraryV07 calls `latestRoundData()` but discards `updatedAt` return value. No check of the form `require(updatedAt >= block.timestamp - maxAge)`. The contract accepts any price regardless of how stale. | FeeLibraryV07 BaseScan: `(, int256 price, , ,) = AggregatorV3Interface(priceFeed).latestRoundData();` — 4th return value (updatedAt) ignored. `require(price >= 0)` is the only validation. | RED
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 →