Aave Protocol V3 Technical Paper

Authors Emilio Frangella and Lasse Herskind
Year 2022 (January 27)
Project Aave V3
License Not stated in the paper
Official Source Aave V3 Technical Paper (PDF)

This page is an educational summary and analysis of an official whitepaper or technical paper, written for reference purposes. It is not a verbatim reproduction. CryptoGloss does not claim authorship of the original work. All intellectual property rights remain with the original author(s). The official document is linked above.

Original paper Original paper
Directories Ethereum Whitepapers & Research

Aave V3’s technical paper, written by Emilio Frangella and Lasse Herskind and dated January 27, 2022, describes a redesign of Aave’s lending markets. It focuses on capital efficiency, protocol safety, decentralization, and user experience. The paper is a historical design document; it should not be read as a complete description of every current Aave deployment.

Aave V3 remains an active protocol version, but it has changed since the paper appeared. Aave’s official changelog records a V3.7 rollout across listed markets in April and May 2026, while V4 is a separate version with a hub-and-spoke design. Check the documentation for the specific market and date when a current parameter matters.

Publication and scope

The paper groups its goals around capital efficiency, protocol safety, decentralization, and user experience. Its main design areas include Efficiency Mode (eMode), isolated collateral settings, cross-chain Portals, and per-asset supply and borrow caps. Some of these mechanisms were later revised; the paper explains the original design, not an unchanging feature set.

Efficiency Mode (eMode)

eMode organizes assets into risk categories so that eligible collateral and borrow assets can use category-specific Loan-to-Value (LTV), liquidation-threshold, liquidation-bonus, and borrowing-permission settings. A user selects a category, and borrowing is limited to the assets allowed by that category. This can increase borrowing power for assets treated as correlated, but the permitted assets and risk parameters differ by category and market. The paper’s design does not make a quoted high LTV universal or remove liquidation risk; correlated assets can diverge in price, liquidity, or market behavior.

Later V3 documentation describes liquid eModes, where an asset may be available in more than one category. The current category parameters and eligible assets should be checked in Aave’s live documentation before relying on a particular configuration.

Isolation Mode: original design and later changes

The original V3 design allowed a market to list a higher-risk asset as isolated collateral. Its debt ceiling limited borrowing against that asset, and only approved assets could be borrowed while it was used as collateral. The design sought to contain one asset’s risk rather than letting it share every collateral combination.

Aave V3.7 later changed this part of V3. Aave’s governance proposal describes removing the older isolated-collateral and borrowable-in-isolation settings while adding an isolated flag to eMode categories. The official changelog records V3.7 deployments across specified markets in 2026. Treat the paper’s Isolation Mode description as the original design; check the exact deployment and market documentation for today’s controls.

Portals and cross-chain liquidity

The paper describes Portals as a way for governance-approved bridge integrations to move Aave liquidity across deployments. In the design, an approved integration can create a temporary unbacked position on a destination market, then settle the related credit through the bridge flow. This is different from an ordinary user moving collateral between chains in one trustless transaction: the bridge, authorization, and settlement process introduce additional assumptions. The paper documents the design and does not establish that any named bridge integration is currently available.

Supply and borrow caps

Supply caps limit how much of an asset can be supplied to a market; borrow caps limit how much can be borrowed. These are configurable risk controls applied to particular assets and deployments. They can help limit concentration, but they are not fixed protocol-wide guarantees and do not prevent price, oracle, liquidity, smart-contract, or governance risks.

Developments after the paper

GHO and later V3 upgrades are developments after this 2022 paper, not features the paper originally specified. The V3.7 rollout revised parts of the original isolation design. Aave V4 launched on Ethereum in March 2026 with a different hub-and-spoke liquidity architecture and later expanded to additional markets. V3 and V4 are distinct versions; a feature or setting in one should not be assumed to apply to the other.

Risks and limitations

Aave lending is exposed to collateral-price changes, oracle behavior, liquidity conditions, liquidation mechanics, smart-contract defects, and governance decisions. Category-specific LTVs can increase capital efficiency while leaving less room for a price move before liquidation. A debt ceiling limits one configured borrowing pathway; it is not a promise that total losses from every failure mode cannot exceed that amount. Cross-chain designs add bridge and settlement risks. These are design considerations, not a claim that a specific current market is unsafe.

Social Media Sentiment

A small Reddit discussion in r/defi asked when lending on Aave would feel safe again. Several commenters focused on uncertainty, residual risk, and whether yield justified exposure; a later reply said conditions were improving. This is a limited snapshot from one discussion during a particular period, not a representative view of Aave users and not an assessment of the protocol’s current safety.

Last updated: 2026-10

Related Terms

See Also

Research