Oracle staleness check present
Veda (BoringVault)'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 #
The AccountantWithRateProviders enforces minimumUpdateDelayInSeconds (minimum elapsed time between rate updates) but does NOT check Chainlink updatedAt freshness on underlying feeds. Chainlink staleness detection relies on the off-chain rate updater operator. No on-chain updatedAt > now - X check found in contract source.
Sources #
- GitHubAccountantWithRateProviders.sol sourceAccountantWithRateProviders.sol _beforeUpdateExchangeRate — checks currentTime < state.lastUpdateTimestamp + state.minimumUpdateDelayInSeconds; no updatedAt checkretrieved 2026-05-17
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 veda factor RD-F-059 score yellow collected_at 2026-05-17 12:41:22