Oracle pool depth (USD)

Uniswap (v2 + v3)'s assessment for RD-F-055 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

No upstream DEX-TWAP oracle consumed by V2 or V3. V2 and V3 ARE the pools that downstream TWAP consumers read. No upstream pool depth to measure for V2 or V3's own risk.

Detail #

V2 and V3 are oracle providers (outbound TWAP service), not oracle consumers. The concept of 'oracle pool depth' measures the depth of an upstream pool feeding an oracle into this protocol — that upstream relationship does not exist for V2 or V3.

Sources #

Curator note
Profile §7 — Oracle topology: providers not consumersV2 and V3 are the TWAP oracle providers, not consumers. No upstream pool concept applies. Downstream consumers' pool-depth risks are their own Cat 3 concerns.retrieved 2026-05-12

Methodology #

Measure the liquidity depth of each DEX pool feeding a TWAP oracle, in USD at reference block; updated continuously.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol uniswap factor RD-F-055 score not_applicable collected_at 2026-05-12 10:36:11