Skip to main content
Aave V3 is one of the protocols in Otto’s live yield discovery service. For the distinction between discovery and executable venues, see the Earning Yield guide.
Key Capabilities
  1. Live Aave Discovery: Otto reads Aave V3 supply markets and compares their net APYs across the discovery service’s supported chains.
  2. Registry-Bound Execution: The executable DApp rail is narrower than discovery: it accepts only the pinned Aave V3 · Base · USDC market, and only while the unified Otto session is ARMED and the discovery row matches the server registry exactly.
  3. Input Filters: Discovery drops non-positive or implausible APYs, and applies a $1 million TVL floor whenever the source provides TVL. These are data-quality filters, not a guarantee of safety or returns.
Discovery Chains: Ethereum, Base, Arbitrum, Polygon, Optimism, and Avalanche. DApp execution: Base USDC only. How to Lend
  1. Open /app Mission Control and inspect the Featured Yield card. The venue table is live discovery; rows that are not registry-backed are display-only.
  2. Check the executable row: The deposit control targets the card’s current top venue. Proceed only when it shows AAVE V3 · BASE USDC · PINNED EXECUTION; the venue rows are not a manual pool picker.
  3. Arm and review: The unified Otto session must be ARMED. Review the venue, current APY, asset, and amount before submitting.
  4. Deploy: Enter the USDC amount and select DEPLOY · UNIFIED ARM. Once the unified session is armed, the supported deposit does not ask for a second owner signature at click time.
The standalone Yield Copilot mini-agent page is discovery-only. Registry-bound deposits are live from the Featured Yield card for its current exact Base USDC Aave or Morpho row; auto-rebalance and alerts remain disabled.
This integration separates broad Aave discovery from a narrowly identified Base USDC execution route.