TWAP window duration
Beefy Finance's assessment for RD-F-054 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
CLM onlyCalmPeriods: 60-second Uniswap V3 TWAP window — materially below the 30-minute (1800-second) safe threshold and below the red threshold of 10 minutes (600 seconds). 60 seconds = 1 minute. BeefySwapper DEX-TWAP periods: configurable per token with NO minimum period enforced in validateData() — zero or sub-60-second periods are technically acceptable in the contract.
Sources #
- DocsBeefy CLM product docs — TWAP window specificationCLM documentation explicitly states '60 seconds' TWAP window for calm period detectionretrieved 2026-05-16
- BeefyOracleUniswapV3.sol — TWAP period validation gapBeefyOracleUniswapV3.sol validateData() — no minimum twapPeriod check; accepts any uint32 valueretrieved 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 beefy factor RD-F-054 score red collected_at 2026-05-16 13:10:30