Single-pool oracle (no medianization)

Beefy Finance's assessment for RD-F-056 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

BeefyOracle: each token maps to ONE sub-oracle with no medianization or cross-venue aggregation (source: 'each token maps to one SubOracle containing one oracle address'). CLM: single Uniswap V3 pool's TWAP with no cross-validation. No multi-source aggregation at any level in the BeefyOracle system.

Sources #

Docs
Beefy CLM — single-pool oracle referenceCLM docs — single pool TWAP reference for calm-period detection, no cross-venue validationretrieved 2026-05-16
GitHub
BeefyOracle.sol — single-source oracle designBeefyOracle.sol — 'single sub-oracle per token, no aggregation across multiple sources'retrieved 2026-05-16

Methodology #

Determine whether the oracle reads from a single DEX venue with no medianization across multiple pools or venues.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol beefy factor RD-F-056 score red collected_at 2026-05-16 13:10:30