Oracle providers used
Uniswap (v2 + v3)'s assessment for RD-F-048 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No external oracle providers consumed by V2 or V3 core contracts. V2 uses constant-product AMM invariant (x*y=k), reading internal _reserve0/_reserve1. V3 uses concentrated-liquidity invariant, reading slot0.sqrtPriceX96. Both EXPOSE TWAP oracles outbound (V2 via cumulative price accumulators; V3 via Oracle.sol observe()) but consume none. 19 Chainlink feeds in data cache cleared as false positives — not called by any V2 or V3 contract.
Detail #
UniswapV2Pair.sol imports: SafeMath, UniswapV2ERC20 (internal only), zero external oracle interfaces. UniswapV3Pool.sol imports: Oracle.sol (internal library), TickMath, SwapMath, SqrtPriceMath, FullMath — all internal, zero Chainlink/Pyth/RedStone interface imports. Profile meta.json oracle_topology: v2_consumes_oracle: false, v3_consumes_oracle: false. Data cache coverage_flags.lending_protocol: false.
Sources #
- GitHubUniswapV2Pair.sol source — v2-coreUniswapV2Pair.sol — zero external oracle imports; reserve reads are internal state variablesretrieved 2026-05-12
- UniswapV3Pool.sol source — v3-coreUniswapV3Pool.sol imports: Oracle.sol (internal lib), TickMath, SwapMath, SqrtPriceMath — all internal. Zero external oracle interfaces.retrieved 2026-05-12
- Profile meta.json oracle_topology sectionProfile §7 oracle_topology: v2_consumes_oracle: false, v3_consumes_oracle: false. Data cache oracle_feeds 19 entries confirmed false positives per profile §7 flag data_cache_oracle_feeds_likely_false_positives: true.retrieved 2026-05-12
Methodology #
List all oracle providers used (Chainlink, Pyth, Redstone, Uniswap-TWAP, in-house, etc.) per asset/market pair in the protocol.
See the full factor methodology and distribution across all protocols →