Oracle staleness check present

Spiko's assessment for RD-F-059 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Staleness check present: ATM3.sol require(block.timestamp < updatedAt + oraclettl, 'oracle value too old'); MultiATMLinear.sol require(block.timestamp < updatedAt + oracleTTL, OracleValueTooOld(oracle)). Both subscription/redemption contracts validate oracle recency before using price data. oraclettl is configured at construction.

Sources #

GitHub
MultiATMLinear.sol — spiko-tech/contracts GitHubMultiATMLinear.sol _getPrices(): require(block.timestamp < updatedAt + oracleTTL, OracleValueTooOld(oracle))retrieved 2026-05-16
GitHub
ATM3.sol — spiko-tech/contracts GitHubATM3.sol _getPrices(): require(block.timestamp < updatedAt + oraclettl, 'oracle value too old')retrieved 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 →

rubric_version v1.7.0 protocol spiko factor RD-F-059 score green collected_at 2026-05-15 22:52:13