Oracle staleness check present

Centrifuge's assessment for RD-F-059 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

No staleness check in V3 core contracts. OracleValuation.sol stores prices with only a validity flag (price.isValid) — no timestamp-based age check. SimplePriceManager similarly has no updatedAt > now - maxAge guard. ShareClassManager.sol records a computedAt timestamp but does not reject stale prices. No freshness threshold enforcement found.

Sources #

GitHub
https://github.com/centrifuge/protocol/blob/main/src/valuations/OracleValuation.solretrieved 2026-04-27
GitHub
https://github.com/centrifuge/protocol/blob/main/src/managers/hub/SimplePriceManager.solretrieved 2026-04-27

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 centrifuge factor RD-F-059 score red collected_at 2026-04-30 21:19:10