Oracle-manipulation-proof borrow cap
Jupiter'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 #
Jupiter Lend: per-asset borrow caps not publicly disclosed as of assessment date; Fluid architecture uses 'dynamic limits' but specifics are not enumerable from public sources. Jupiter Perps: $2.5M per-position cap and pool AUM cap (maxAumUsd) documented — these implicitly limit oracle manipulation payoff. Factor definition (borrow cap <= oracle pool depth × manipulation-resistance multiplier) is designed for lending protocols with per-asset borrow caps — not directly applicable to Perps or Aggregator. Lending product caps partially applicable but undisclosed. Treating as not_applicable pending public disclosure of per-asset borrow caps.
Sources #
- DocsJupiter Perpetuals Pool Account: maxPositionUsd = $2.5M, maxAumUsd cap documentedJupiter Perps pool account docs — maxPositionUsdretrieved 2026-04-29
- No public documentation of per-asset borrow caps for Jupiter Lend markets foundJupiter Lend borrow caps not publicly disclosedretrieved 2026-04-29
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 →