Oracle staleness check present

Evidence summary #

Oracle published every ~3 seconds by validators. No documented staleness rejection mechanism — unclear what happens if validator oracle submissions stop (network partition, coordinated liveness failure). The 3-second cadence suggests real-time tracking of CEX prices but does not confirm a staleness guard. Bridge2 is unaffected (no oracle used). Low confidence due to closed-source L1 binary.

Sources #

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 →