TWAP window duration
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-054 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Kashi uses Chainlink spot price (via ChainlinkOracleV1 calling latestRoundData) — NOT a TWAP. No TWAP window configured. Kashi's design is Chainlink-point-in-time pricing, which is standard for Chainlink-based lending protocols but means no TWAP protection against short-duration price manipulation. AMM core: no TWAP required (internal pool math). Scored yellow: absence of TWAP in a lending context is a risk even with a reputable oracle, especially combined with missing staleness check (F059 red).
Sources #
- EtherscanChainlinkOracleV1 Etherscan — function signatures confirm non-TWAP designChainlinkOracleV1 0xd766147bc5a0044a6b4f4323561b162870fcbb48 ABI — peek/get functions call Chainlink latestRoundData, no TWAP accumulatorretrieved 2026-05-17
- Sushi Integrates Chainlink Price FeedsSushi Chainlink integration — confirms point-in-time Chainlink feed usageretrieved 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 →