TWAP window duration
Save (formerly Solend)'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 #
Save uses Pyth Network and Switchboard — both are off-chain aggregated price oracles, not DEX TWAP mechanisms. The processor.rs get_pyth_price() reads from Pyth Price account data structures (slot-based staleness, no TWAP computation). get_switchboard_price() reads AggregatorAccountData (aggregated from multiple configured sources, not a TWAP). TWAP window duration is not applicable to the oracle architecture used.
Sources #
- GitHubSolend processor.rs — oracle implementation (no TWAP)processor.rs get_pyth_price() — reads Price struct with slot staleness check; no TWAP computation; processor.rs get_switchboard_price() — reads AggregatorAccountData float; no TWAPretrieved 2026-05-17
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 →