Fallback behavior on oracle failure
Spiko's assessment for RD-F-051 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
ATM3.sol and MultiATMLinear.sol revert (halt) if oracle is stale beyond oraclettl. No fallback to secondary source — just revert. Users cannot subscribe or redeem when oracle is stale (weekends, holidays). No last-known-price mode. This is a known operational gap for business-day-only NAV publishing.
Sources #
- GitHubMultiATMLinear.sol — spiko-tech/contracts GitHubMultiATMLinear.sol _getPrices(): require(block.timestamp < updatedAt + oracleTTL, OracleValueTooOld(oracle)) — same revert patternretrieved 2026-05-16
- ATM3.sol — spiko-tech/contracts GitHubATM3.sol _getPrices(): require(block.timestamp < updatedAt + oraclettl, 'oracle value too old') — revert on staleness, no fallbackretrieved 2026-05-16
Methodology #
Identify the declared fallback behavior (pause, secondary source, last-known-price, revert) when the primary oracle reverts or reports a stale value.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol spiko factor RD-F-051 score yellow collected_at 2026-05-15 22:52:13