Oracle staleness check present
Ondo 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 #
**No on-chain staleness check for OUSG Pricer or USDY RWADynamicOracle.** The RWADynamicOracle serves prices based on time-range formula — if a range expires without being replaced, the formula continues from last configured range but may be stale relative to actual NAV. No `updatedAt` freshness enforcement in the consuming contracts (InstantManager). Flux Finance uses Chainlink feeds; evidence suggests Compound v2 fork pattern — FluxOracle uses `latestAnswer()` (deprecated) rather than `late...
Sources #
- EtherscanRWADynamicOracle (verified: 'Ondo Finance: USDY Price Oracle')https://etherscan.io/address/0xa0219aa5b31e65bc920b5b6dfb8edf0988121de0retrieved 2026-05-12
- OUSG_InstantManager (verified: 'Ondo Finance: OUSG Instant Manager 2')https://etherscan.io/address/0x93358db73B6cd4b98D89c8F5f230E81a95c2643aretrieved 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 →