Oracle staleness check present
mETH Protocol'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 #
Oracle.sol enforces finalization delay: rejects records where block.number < updateEndBlock + finalizationBlockNumberDelta (~64 blocks, ~2 epochs). This prevents use of unfinalized data. However, there is NO explicit heartbeat check for delivery staleness — if the oracle committee goes offline, the rate freezes at the last valid record indefinitely. Users relying on an up-to-date exchange rate would be operating on stale data without any protocol alarm.
Sources #
- GitHubOracle.sol finalization + stalenessmantle-lsp/contracts src/Oracle.sol — finalizationBlockNumberDelta enforcement; no heartbeat staleness check on oracle delivery silenceretrieved 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 →