Oracle staleness check present
Euler V2'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 #
ChainlinkOracle: staleness check present — reverts with PriceOracle_TooStale when block.timestamp - updatedAt > maxStaleness. PythOracle: staleness check present (maxStaleness capped at 15 min). UniswapV3Oracle: no explicit staleness check — relies on TWAP period. Chainlink USDT/USD maxStaleness = 86400s (24h) per data-cache heartbeat; USDC/USD = 82800s (23h). These generous thresholds allow significant staleness windows before revert — up to 24h for stablecoin feeds. Taxonomy threshold for volatile assets is 3600s; stablecoins exceed this significantly.
Sources #
- GitHubChainlinkOracle — Staleness Check ImplementationChainlinkOracle.sol _getQuote() staleness check: block.timestamp - updatedAt > maxStaleness → revertretrieved 2026-05-04
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 →