Oracle-manipulation-proof borrow cap
Maple Finance'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 #
Not applicable. Maple uses Chainlink push-oracle price feeds (not DEX TWAP) for collateral valuation. Borrow caps are negotiated per-borrower by Pool Delegates. Oracle-manipulation-proof borrow cap vs. DEX pool depth check does not apply to this architecture.
Detail #
Data-cache oracle_feeds[] lists Chainlink feeds for ETH/USD, BTC/USD, USDC/USD, USDT/USD, LINK/USD, UNI/USD, AVAX/USD, COMP/USD. Maple explicitly uses 3 independent price feed sources per its risk management docs. Per-borrower borrow caps are set by Pool Delegates through credit assessment, not through on-chain oracle-pool-depth arithmetic.
Sources #
- Partner feed00-data-cache.json oracle_feeds arraydata-cache oracle_feeds[] - Chainlink feeds enumeratedretrieved 2026-04-27
- Yield Generation, Underwriting and Risk Management - Maple FinanceMaple yield/underwriting - 3 independent price feedsretrieved 2026-04-27
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 →