Oracle staleness check present

Lista DAO'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 #

ResilientOracle has timeDeltaTolerance staleness check (returns INVALID_PRICE if block.timestamp - updatedAt > tolerance). Confirmed at aggregator level. However: PythOracle.sol uses getPriceUnsafe() with no staleness check at adapter level. BnbOracle.sol and SlisBnbOracle.sol have no adapter-level staleness check. AVAX/USD and COMP/USD have 86,400s (24h) Chainlink heartbeat — stale window very wide. Yellow: staleness present at aggregator but absent at several adapter and feed levels.

Sources #

GitHub
Lista DAO PythOracle.sol — getPriceUnsafe confirmedcontracts/oracle/ResilientOracle.sol — timeDeltaTolerance confirmed; contracts/oracle/PythOracle.sol — getPriceUnsafe confirmedretrieved 2026-05-12
Internal
Lista DAO data cache AVAX/COMP heartbeats00-data-cache.json sources.oracle_feeds — AVAX/USD 86400s heartbeat confirmedretrieved 2026-05-12

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 lista-dao factor RD-F-059 score yellow collected_at 2026-05-12 17:54:05