Oracle staleness check present
OpenEden'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 #
Vault staleness check present: if (block.timestamp - updatedAt > 7 days) revert TBillPriceOutdated(updatedAt). Threshold is 7 days (604,800 seconds). This is wide for a daily-push NAV oracle — best practice would be 24–48 hours. However, for a T-bill NAV oracle subject to bank holidays and weekend closures, a 7-day window has documented operational rationale (3-day buffer mentioned in source context). Not red (check exists and halts on staleness), but yellow (threshold wider than best practice).
Sources #
- EtherscanOpenEden Vault V4/V5 Implementation — staleness check confirmedOpenEdenVaultV4Impl.sol tbillUsdcRate(): 7-day staleness check confirmed; TBillPriceOutdated error with updatedAt parameterretrieved 2026-05-16
- OpenEdenVaultV4Impl.sol — GitHub sourceOpenEdenVaultV4Impl.sol in audit repo: tbillUsdcRate() 7-day threshold with 3-day holiday buffer rationale noted in source commentsretrieved 2026-05-16
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 →