Oracle staleness check present
Cap (cUSD / stcUSD)'s assessment for RD-F-059 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
_isStale(address _asset, uint256 _lastUpdated) in PriceOracle.sol checks block.timestamp - _lastUpdated > staleness[_asset]. Staleness thresholds set per asset by admin via setStaleness(address _asset, uint256 _staleness). Mint and burn functions disabled when oracle returns stale data per docs. Staleness check is present on both primary and backup oracle reads.
Sources #
- URLCap documentation on oracle stale behaviordocs.cap.app: 'Mint and burn functions are disabled if Oracle prices are stale, until Oracles are back in sync'retrieved 2026-05-17
- PriceOracle.sol staleness check implementationPriceOracle.sol _isStale() function: block.timestamp - _lastUpdated > staleness[asset]; setStaleness() admin functionretrieved 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 cap factor RD-F-059 score green collected_at 2026-05-17 10:56:24