NOUTITA NEWSROOMSTEP-BY-STEP GUIDE

DeFi Lending and Borrowing: How Aave v3 Actually Works

An in-depth, multi-section guide to Aave v3’s lending and borrowing mechanics for the US DeFi market. We dissect core invariants, risk controls, and practical steps to lend, borrow, or manage positions across networks—grounded in primary docs, GitHub sources, and trusted analytics.

LEARN & GUIDES / TECHNICAL GUIDE

noutita.com#DEFI

# DeFi Lending and Borrowing: How Aave v3 Actually Works

By Marcus V. · US DeFi Strategist

In Brief (TL;DR)

Aave v3 is a multi-chain, non-custodial lending protocol built on smart contracts that enable overcollateralised borrowing and liquidity provision. When you supply, you receive aTokens that accrue interest automatically; your position can be used as collateral for loans. (aave.com)

Loans are secured by collateral whose value must exceed the borrowed amount (overcollateralisation). The safety of a borrow is tracked via a Health Factor; if it drops below 1, liquidation is possible. (aave.com)

Aave v3 introduces risk-segmentation features like EModes (enhanced borrowing parameters for asset classes) and Isolation Mode (restricting how isolated assets can be used as collateral). These are designed to onboard more assets with controlled risk. (github.com)

Across networks, Aave v3 aims to unify liquidity and lending markets, with deployments on Ethereum and many Layer 2s and bridges, enabling cross-chain lending/borrowing experiences. (aave.com)

The core architecture, including aTokens, the reserve pools, and risk parameters like LTV and liquidation thresholds, is documented in the official docs and the Aave V3 Technical Paper. Use these sources for precise numbers per asset. (aave.com)

“Isolation Mode in Aave V3 is designed to safely introduce new or volatile assets into the protocol by limiting how they can be used as collateral.” This framing guides how risk is contained when onboarding new assets. (aave.com)

1. Theoretical Foundations & Invariants

What Aave v3 is (the core concept)

Aave v3 is a collection of self-executing, public smart contracts that enable overcollateralised lending and borrowing without a central intermediary. Users interact via wallets to supply assets, earn yield, and borrow against collateral. The protocol’s design is deployed across multiple networks (e.g., Ethereum, rolling out to Layer 2s and sidechains), enabling cross-chain liquidity and multi-chain markets. (aave.com)

When you supply tokens, you receive aTokens (e.g., aETH, aUSDC). These interest-bearing tokens track your share of the pool and accrue yield automatically. You can withdraw anytime if there is available liquidity in the pool. (aave.com)

Borrowing requires collateral, with the caveat that the collateral value must exceed the loan value (overcollateralisation). The LTV for each asset defines how much you can borrow against it; as collateral values swing, the loan’s risk is monitored via a “health factor.” (aave.com)

The safety envelope includes a liquidation mechanism: if your health factor falls below a threshold (HF < 1), liquidators can repay debt and seize collateral at a discount, incentivizing corrective action and protecting the protocol. (aave.dev)

Key invariants and metrics you must know

Loan-to-Value (LTV) and liquidation threshold are asset-specific risk parameters that determine how much you can borrow and when liquidation becomes a threat. These are configured per asset in each pool and are central to risk controls. (aave.com)

Health Factor (HF) is a real-time risk metric used to decide when a position is undercollateralised. It combines collateral value, LTV, and debt value to indicate safety; a drop below 1 can trigger liquidation. The concept and calculation are documented in Aave materials and developer resources. (aave.dev)

The v3 stack retains established features (aTokens, instant liquidity, native stable-rate borrowing, credit delegation) while adding governance-friendly risk enhancements and cross-chain capabilities. This combination enables more flexible use cases without sacrificing safety. (governance.aave.com)

aTokens, pools, and the mechanics of supplying

Supplying assets yields a corresponding amount of aTokens, which automatically accumulate interest and represent your claim on the pool. Redeeming liquidity involves burning aTokens in exchange for the underlying asset. This mechanism links your yield to the pool’s utilization rate and demand. (aave.com)

The pool architecture centralizes risk and liquidity: each asset has a reserve with a separate supply and borrow dynamic, governed by on-chain parameters and governance. The core contracts and market configurations live in Aave’s v3 core repositories. (github.com)

EModes and risk segmentation (enhanced borrowing)

EModes allow users to gain higher borrowing power for certain asset classes by selecting enhanced LTV/threshold parameters for assets within an eMode category. This is a core feature for onboarding correlated assets (e.g., ETH-correlated) while managing cross-asset risk. The isolated variant of EModes adds an “isolated” flag, further tightening which collateral can contribute to borrowing power. (github.com)

The governance and configuration path for EModes includes changes to categories, collateral lists, and the potential to isolate or un-isolate an eMode. This is part of the ongoing evolution of Aave v3’s risk model. (github.com)

Isolation Mode further narrows which assets can be used as collateral and which can be borrowed, aiming to contain risk when onboarding new or volatile assets. (aave.com)

Cross-chain design: liquidity across networks

Aave v3 is not limited to a single chain; the protocol has deployed across Ethereum and numerous Layer 2s and sidechains to create a more seamless liquidity experience, with cross-chain features that are enabled by governance and the Portal/bridging concepts. This multi-chain (and multi-network) approach is a deliberate design choice to increase capital efficiency. (aave.com)

The cross-chain data and analytics literature also highlights how Aave V3 enables multi-chain lending/borrowing across a broad set of networks, reflecting real-world usage patterns and liquidity integration. (arxiv.org)

Core contracts, risk controls, and governance interplay

The Aave v3 core contracts, including the Pool, configurators, and asset risk parameters, are maintained in official GitHub repositories. The code governs lending/borrowing, liquidations, and risk parameter updates. (github.com)

The asset registry (Aave Address Book) helps integrators locate the correct contract addresses for each market and asset on a given network, boosting interoperability and safety for developers. (github.com)

Governance proposals and risk parameter discussions (e.g., risk parameter methodologies, isolated eMode, and EModes) are published and debated in the Aave governance forums. These discussions shape how v3 evolves over time. (governance.aave.com)

Focus on risk and transparency

Aave maintains a risk framework and publishes risk parameter docs to communicate how assets are evaluated and onboarded, including thresholds, LTVs, and liquidation rules. This is central to the protocol’s reliability narrative in DeFi risk management research. (github.com)

Security considerations and third-party audits contribute to the trust layer for Aave v3 products across networks. Regular security reviews and contract audits are part of the lifecycle. (aave.com)

2. Step-by-Step Tutorial (Practice)

A. Prerequisites & Security

Have a modern Web3 wallet (e.g., MetaMask) connected to a supported network where Aave v3 is active (Ethereum and/or a supplied Layer 2). The official introduction notes that Aave v3 operates across Ethereum and multiple networks, including L2s and rollups. This matters for gas efficiency and user experience. (aave.com)

Understand the fundamental risk controls before you start: LTVs are asset-specific and determine borrowing power, while the Health Factor tracks safety of your position. You should monitor HF to avoid forced liquidations. (aave.com)

Review Isolation Mode documentation if you’re considering onboarding new or volatile assets. Isolation Mode restricts collateral and borrowing to a curated set of assets approved by governance. This is a cautionary design to limit systemic risk. (aave.com)

Security posture and best practices: read Aave’s security page and related developer guidelines to understand how contracts are secured and how to respond to on-chain risk alerts. (aave.com)

B. Executing the Steps

1) Connect and choose the market

Visit the Aave interface on a network where v3 is deployed and connect your wallet. Selecting the proper market and network is essential because each network may have different assets, pools, and risk parameters. The multi-network design is explicitly called out in Aave’s introductory material. (aave.com)

2) Supply assets and receive aTokens

Pick an asset you want to supply (e.g., ETH, USDC). When you supply, you will receive aTokens in return (e.g., aETH, aUSDC). These aTokens accrue interest automatically and represent your claim on the pool. You can withdraw by redeeming aTokens back to the underlying asset, subject to available liquidity. (aave.com)

Important nuance: the balance of aTokens grows with accrued interest, and the underlying liquidity is governed by pool utilization. High utilization drives up interest rates; low utilization lowers them. This dynamic helps balance supply and demand. (aave.com)

3) Borrow against your collateral

After supplying collateral, you can borrow assets up to the limit imposed by the asset’s LTV and the pool’s health. The borrowing power is asset-specific and subject to the current health of your position. If your collateral value falls or debt grows, your HF would adjust accordingly. (aave.com)

The borrowing process transfers the borrowed assets to you, and your collateral balance remains locked until you repay. Interest accrues on the borrowed amount, and your collateral cannot be transferred while the loan is open. (aave.com)

4) Manage risk while borrowing

The Health Factor is the primary on-chain metric you should monitor. It is calculated from your collateral, LTVs, and debt; a HF below 1 makes you vulnerable to liquidation. Monitor HF through the Pool contracts and associated dashboards or subgraphs. (aave.dev)

5) Repay the loan and withdraw collateral

Repay principal plus accrued interest to unwind a borrow position. Once the debt is fully repaid, you can withdraw your collateral by burning the corresponding aTokens. The Aave docs describe this flow for users. (aave.com)

6) Advanced features you may leverage (caution advised)

EModes: select an asset class category to unlock enhanced borrowing parameters for assets within that class. This can increase borrowing power for correlated assets, but requires careful risk assessment and governance-approved configurations. Isolated eMode adds an extra layer of isolation for certain assets and can restrict non-listed collateral. (github.com)

Isolation Mode: onboard and use isolated collateral assets only for specific, governance-approved borrowings. Isolation Mode is explicitly designed to contain risk when onboarding volatile assets. (aave.com)

7) Governance and on-chain liquidity awareness

Asset lists, risk parameters, and eMode configurations are governed through on-chain governance processes and documented proposals. Keeping abreast of governance discussions helps you anticipate parameter changes that affect borrowing power and risk. (governance.aave.com)

C. Practical considerations for builders and users

If you’re integrating with Aave v3 as a developer, consult the GitHub repositories for core contracts and the Aave Address Book to locate the correct addresses on a given network. This ensures you reference the right LendingPool, Reserve, and aToken contracts when building tooling or dashboards. (github.com)

For on-chain verification and auditing, you can review the v3 core code and the accompanying audits to understand the risk controls and upgrade paths. This is essential for risk-aware integrations and for planning future deployment strategies. (raw.githubusercontent.com)

Etherscan pages provide a window into verified contract addresses and their interactions on mainnet with Aave v3. While not a substitute for docs, they offer a practical snapshot of contract activity. (etherscan.io)

If you’re exploring cross-chain liquidity effects or analytics, consult cross-chain research and L2 ecosystems to understand where Aave v3 markets are active and how liquidity migrates across networks. Academic and industry analyses underscore the multi-chain nature of Aave v3 and its impact on liquidity distribution. (arxiv.org)

D. Common misconceptions and defensive plays

Misconception: All assets can be borrowed against all other assets through a single, universal LTV. Reality: LTV is asset-specific, and EModes or Isolation Mode can further constrain how collateral may be used for borrowing. Always verify the asset-specific LTV and whether the asset is included in any active eMode category before borrowing. (aave.com)

Misconception: Liquidity is always plentiful. Reality: Interest rates move with pool utilization. In high-demand markets, supply and borrow dynamics can shift quickly, affecting APYs and loan affordability. This behavior is built into the pool logic and is a deliberate design to balance liquidity. (aave.com)

Quick Reference: Where to Find It (sourcing you can trust)

Aave v3 Introduction and Help Center: Introduction to Aave V3; Isolation Mode; general lending/borrowing concepts. (aave.com)

Aave v3 Core GitHub and registries: Core smart contracts and address book for integration work. (github.com)

Aave Governance and risk parameter discussions: Proposals and risk parameter methodologies. (governance.aave.com)

Cross-chain and multi-network deployment coverage: Arbitrum blog and L2 ecosystem references. (aave.com)

Aave V3 Technical Paper (for architecture) and health-factor-based risk framing: Technical overview and risk discussions. (raw.githubusercontent.com)

Final Notes

Aave v3 represents a mature yet evolving blend of longstanding DeFi primitives (aTokens, instant liquidity, credit delegation) with sophisticated risk controls (EModes, Isolation Mode, health-factor-based liquidations) and cross-chain liquidity. The literature and codebase reveal a deliberate emphasis on transparency, governance-driven risk management, and multi-network operability. For practitioners, the key to a safe, productive experience is understanding asset-specific LTVs, monitoring health factors, and choosing the right mode (standard, eMode, or isolated) for the asset class you are handling. (raw.githubusercontent.com)