Oracle staleness check present

ether.fi'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 #

EtherFiOracle enforces _isFinalized() check (epoch+2 minimum before publication), preventing premature reports. No updatedAt > now - X staleness guard found on the LiquidityPool consumer side. Committee-based model assumes freshness via quorum liveness — if committee reports regularly, staleness is not a concern; if quorum fails, rebase halts (protocol suspended) rather than using a stale price. No consumer-side staleness rejection implemented.

Sources #

Etherscan
EtherFiOracle implementationEtherFiOracle implementation — _isFinalized() epoch+2 checkretrieved 2026-04-28
GitHub
LiquidityPool.solLiquidityPool.sol — no updatedAt staleness guard foundretrieved 2026-04-28

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 ether-fi factor RD-F-059 score yellow collected_at 2026-04-28 13:58:46