Oracle-manipulation-proof borrow cap
Uniswap (v2 + v3)'s assessment for RD-F-073 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Lending-only factor (taxonomy PD-024). No borrow caps in V2 or V3. Neither version consumes any external oracle for swap pricing — both are price discovery mechanisms. Data cache oracle_feeds entries are false positives (feeds reading V2/V3 pool prices, not consumed by core contracts).
Detail #
Taxonomy §Category 4 PD-024: lending-only. Data cache borrow.present=false. Profile oracle_topology: v2_consumes_oracle=false, v3_consumes_oracle=false. The 19 Chainlink feeds in data cache are false positives per profile §7: 'these appear to be feeds that read V3 pool prices or are associated with the Uniswap interface — NOT feeds that V3 core contracts consume.' No oracle-manipulation borrow cap calculation applies.
Sources #
- Curator noteTaxonomy PD-024 + oracle topologyTaxonomy PD-024 lending-only; profile oracle_topology.v2_consumes_oracle=false, v3_consumes_oracle=false; data cache oracle_feeds=false positives per profile §7retrieved 2026-05-12
Methodology #
Determine whether the per-asset borrow cap is ≤ (oracle pool depth × manipulation-resistance multiplier).
See the full factor methodology and distribution across all protocols →