TWAP window duration

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

Evidence summary #

Spiko uses issuer-attested NAV oracle, not a DEX TWAP. TWAP window concept does not apply. Staleness is controlled by oraclettl parameter in ATM3/MultiATMLinear contracts.

Sources #

GitHub
ATM3.sol — spiko-tech/contracts GitHubATM3.sol uses oraclettl (staleness TTL) not a TWAP window; Oracle.sol publishPrice has no TWAP logicretrieved 2026-05-16

Methodology #

For each DEX-TWAP oracle, measure the TWAP window duration in minutes; flag any window < 30 minutes as high risk.

See the full factor methodology and distribution across all protocols →

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