Oracle staleness check present
Frax 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 #
Fraxlend staleness checks confirmed per documentation: prices considered bad/stale if Chainlink signals bad or 'price is too old'; uses latestRoundData() (not deprecated latestAnswer()). isBadData flag propagates from dual-oracle comparison. However, specific maxStaleness value in seconds not confirmed from on-chain read. BUIDL RedStone TSSO has up to 24h staleness inherent in daily NAV updates — unclear whether Frax's staleness gate triggers on 24h-old BUIDL NAV. Yellow because staleness checks exist for Fraxlend but threshold values are unconfirmed; BUIDL NAV path may have 24h staleness tolerance.
Sources #
- DocsFrax Oracle OverviewFrax Oracle overview — 'prices considered bad/stale if underlying Chainlink oracle signals a price is bad, or if a price is too old'retrieved 2026-05-17
- Code4rena Fraxlend 2022 Audit ReportCode4rena Fraxlend 2022 — confirms latestRoundData() usage (not deprecated latestAnswer)retrieved 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 →