Oracle staleness check present
Yearn Finance'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 #
Vault core (V2 + V3): no oracle consumed — staleness check not applicable to vault pricePerShare. Strategy-level: cache identifies Chainlink feeds with heartbeats ranging from 3600s (ETH/USD, BTC/USD, COMP/USD) to 86400s (USDT/USD, AVAX/USD). USDC/USD heartbeat 82800s (23h). Whether individual strategies check updatedAt > block.timestamp - maxStaleness is strategy-specific and not verified at framework level. V2 BaseStrategy.sol and V3 BaseStrategy.sol impose no staleness check requirement. TECH_SPEC.md confirms no staleness checks at spec level. Yellow: strategy-level staleness check not mandated; feeds with 24h heartbeats (USDT/USD, AVAX/USD) are at higher staleness risk if strategies rely on them without checks.
Sources #
- Internal00-data-cache.json oracle_feeds — Chainlink heartbeat datacache sources.oracle_feeds[]: heartbeat_seconds values — USDT/USD 86400s, AVAX/USD 86400s, COMP/USD 3600s, ETH/USD 3600sretrieved 2026-05-16
- Yearn V3 Technical SpecificationTECH_SPEC.md: no staleness checks in V3 vault specretrieved 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 →