Research/Ethereum

Aave v4: Unified Liquidity and Cross-Chain Lending on Ethereum

Aave v4 introduces a unified liquidity layer across chains, aiming to solve DeFi's liquidity fragmentation with a single lending protocol.

bcTanjiNov 17, 2026

DeFi lending generates billions in annual interest, yet the largest protocol in the space spent years fighting itself. Aave v3 launched on over 20 chains, each with its own isolated pool of deposits and borrows. A supplier on Arbitrum earned a different rate than one on Ethereum mainnet for the same asset, and borrowers on Polygon could not tap into idle liquidity sitting on Base. This liquidity fragmentation was not just inefficient: it was structurally limiting Aave's capital efficiency and ceding ground to modular competitors.

Aave v4, which launched on Ethereum mainnet on March 30, 2026, is the protocol's answer. It replaces per-chain pools with a Hub-and-Spoke architecture designed to unify liquidity within each deployment and, eventually, across chains. The upgrade rewrites how risk is isolated, how interest rates are set, and how liquidations work, all while positioning the GHO stablecoin as the native unit tying everything together.

Why Aave v3 Hit a Ceiling

Aave v3 introduced features like efficiency mode (e-Mode), isolation mode, and Portal for cross-chain bridging. These were meaningful improvements, but they shared a fundamental constraint: each chain deployment operated as a standalone lending protocol. Deposits on Optimism could not back loans on Avalanche. Rate curves on each chain reflected only local supply and demand, not the protocol's aggregate position.

The consequences were measurable. With total value locked spread across 20+ chains, no single deployment could offer the depth that a unified pool would provide. Borrowers on smaller chains faced higher rates due to thin supply. Suppliers on larger chains earned lower yields because capital sat idle while demand existed elsewhere. Each new chain deployment required its own governance proposal, risk parameterization, and oracle configuration, creating operational overhead that scaled linearly with chain count.

This fragmentation problem is not unique to Aave. It echoes across DeFi and mirrors challenges in other infrastructure domains. The Ethereum L2 liquidity fragmentation problem describes the same dynamic at the network level: as rollups proliferate, liquidity thins out across venues that cannot natively communicate.

The Hub-and-Spoke Architecture

Aave v4 replaces per-market pools with a layered system of Hubs and Spokes. This is not a cosmetic restructuring: it changes the protocol's unit of liquidity from "one pool per asset per chain" to "one shared pool per network, segmented by risk."

Hubs: The Liquidity Core

A Hub is the central liquidity source on each network. It holds the actual deposited assets and enforces system-wide accounting. Users never interact with the Hub directly. Instead, they supply and borrow through Spokes, which draw on the Hub's shared pool. Governance can deploy multiple Hubs per network, each serving a different function.

On Ethereum, the launch deployment includes three Hubs:

  • Core: the general-purpose Hub that acts as the main source of inter-hub credit lines, serving as the primary venue for standard lending and borrowing
  • Prime: targets suppliers who want ETH and BTC collateral exposure in a non-borrowable, institutional-grade environment without rate volatility from active borrowing
  • Plus: hosts Ethena-related strategies behind dedicated caps, pause conditions, and risk controls

Spokes: Modular Risk Markets

Spokes are the user-facing layer. Each Spoke defines its own collateral types, risk settings, and liquidation rules. The Hub grants each Spoke a credit line for borrowing (how much it can draw from the shared pool) and a debit line for supplying (how much it can contribute). This creates risk isolation without fragmenting liquidity.

The Ethereum launch includes 10 Spokes across the three Hubs, with 7 attached to Core. Some Spokes implement e-Mode for closely correlated asset pairs (like stETH/ETH), while others serve broader lending markets. The key insight: all Spokes on the same Hub share the same underlying pool, so a supplier's deposit backs borrowing across every Spoke connected to that Hub.

Why this matters: In v3, isolating risk meant isolating liquidity. If you wanted to separate a volatile asset into its own pool, that pool had its own supply and demand curve. In v4, isolation happens at the Spoke level while liquidity remains shared at the Hub. Risk segmentation no longer costs capital efficiency.

Unified Accounting: ERC-4626 Shares

Aave v3 used aTokens: rebasing ERC-20 tokens whose balance increased over time to reflect accrued interest. This model was intuitive but created problems for composability. Rebasing tokens interact poorly with many DeFi protocols, requiring wrapper contracts and custom integrations.

Aave v4 replaces aTokens with an ERC-4626-style vault share system. Suppliers receive shares representing their proportional claim on the Hub's assets. Interest accrues to the pool, increasing the value of each share rather than minting new tokens. This standardized interface means any protocol that supports ERC-4626 vaults (yield aggregators, structured products, portfolio managers) can integrate with Aave v4 without custom adapters.

How Liquidations Changed

Aave v3 used a fixed close factor model: when a position's health factor dropped below 1.0, liquidators could repay up to 50% of the debt and claim collateral at a fixed bonus. This created problems at both extremes. For large positions, 50% was often more than needed, resulting in unnecessary collateral loss for borrowers. For positions barely below the threshold, the fixed bonus sometimes failed to attract liquidators fast enough, risking cascading liquidations.

Target Health Factor Model

Aave v4 introduces a target health factor model. Instead of a fixed close factor, liquidators can repay only enough to bring a borrower back to a governance-set target health factor for that Spoke. This means smaller, more precise liquidations when positions are marginally underwater, and larger interventions only when necessary.

Variable Liquidation Bonus

The liquidation bonus in v4 is no longer fixed. It scales with how far below the liquidation threshold a position has fallen, creating a Dutch-auction-like dynamic. Three parameters control this:

  • liquidationBonusFactor: the minimum bonus at the liquidation threshold
  • maxLiquidationBonus: the maximum bonus for deeply underwater positions
  • healthFactorForMaxBonus: the health factor below which the maximum bonus applies

The result is that marginally unhealthy positions get small, cheap liquidations, while severely distressed positions attract aggressive liquidator participation through higher bonuses. Governance can tune these parameters per Spoke, creating borrower-friendly configurations for stable assets and efficiency-focused configurations for volatile ones.

FeatureAave v3Aave v4
Liquidation triggerHealth factor below 1.0Health factor below 1.0
Close factorFixed at 50%Dynamic (target health factor)
Liquidation bonusFixed per assetVariable, scales with health factor
Risk isolationPer-pool isolation modePer-Spoke with shared Hub liquidity
Rate modelGovernance-set slope curvesOn-chain fuzzy logic rate controller
Deposit token standardRebasing aTokens (ERC-20)Vault shares (ERC-4626)
Configuration bindingGlobal per assetDynamic, bound at borrow time

GHO: The Native Stablecoin Thread

GHO is Aave's overcollateralized stablecoin, minted by borrowers who lock collateral in the protocol. Unlike USDC or USDT, GHO does not require external reserves: it is backed entirely by overcollateralized positions within Aave itself. As of mid-2026, GHO's circulating supply sits in the range of 500 to 700 million tokens, depending on the data source and timestamp.

In v4, GHO plays a more structural role. Every Spoke can mint and borrow GHO against its collateral, making GHO the settlement layer that connects otherwise isolated risk markets. New chain deployments no longer need a separate governance proposal for each GHO facilitator: the Hub architecture handles facilitator logic natively.

GHO is currently live on Ethereum, Arbitrum, Base, and Avalanche, with cross-chain transfers handled through Chainlink CCIP. The long-term vision positions GHO as the common unit of account across all Aave deployments, so that cross-chain borrowing and repayment can settle through GHO without requiring asset bridges for every collateral type.

Cross-Chain Liquidity Layer

The Hub-and-Spoke model solves fragmentation within a single network. The Cross-Chain Liquidity Layer (CCLL) is Aave's plan to solve it across networks. The design uses Chainlink's Cross-Chain Interoperability Protocol (CCIP) as the messaging backbone, enabling liquidity fungibility between Hubs on different chains.

In the proposed model, a user could deposit collateral on Arbitrum and borrow against it on Ethereum mainnet, with the CCLL coordinating accounting between the two Hubs. This requires reliable cross-chain messaging with strong finality guarantees, since a failed or delayed message could leave accounting out of sync between chains.

Architecture Challenges

Cross-chain lending introduces risks that do not exist in single-chain protocols:

  • Message latency: cross-chain messages take seconds to minutes, during which asset prices can move enough to make a position liquidatable
  • Oracle inconsistency: price feeds on different chains may diverge, creating arbitrage opportunities or spurious liquidations
  • Bridge risk: the CCLL depends on CCIP's security model, adding a dependency outside Aave's direct control
  • Reorg handling: if a source chain reorgs after a cross-chain borrow is processed, the destination chain holds a loan without valid collateral

The CCLL is not yet live. Aave Labs originally estimated a 2026 or 2027 rollout. The March 2026 Ethereum launch focused on the Hub-and-Spoke model within a single chain, with cross-chain fungibility scheduled for later phases.

Cross-chain composability is a shared challenge: Aave's CCLL design echoes the broader industry push toward cross-chain intent architectures that let users express what they want to accomplish without specifying which chain executes it. Both approaches need the same primitives: reliable messaging, consistent state, and atomic settlement guarantees.

Aave v4 vs. Modular Lending Competitors

Aave v4 does not exist in isolation. Its redesign responds in part to the rise of modular lending protocols, most notably Morpho, that have gained significant market share by offering a different architectural philosophy.

Morpho: Isolated Markets, Composable Risk

Morpho takes the opposite approach from Aave's unified Hub. Instead of pooling liquidity and segmenting risk through Spokes, Morpho creates fully isolated lending markets where each market has exactly one collateral asset and one loan asset. Vault curators then compose these markets into strategies, letting depositors choose their risk exposure.

This design has tradeoffs. Isolated markets concentrate borrow demand into smaller pools, which can produce higher supply rates (Morpho vaults have offered USDC supply rates of 4% to 8.5%, compared to Aave's 3.8% to 6.2%). But isolation also means no shared liquidity: a surge in demand for one market cannot draw on idle capital from another.

DimensionAave v4Morpho
ArchitectureUnified Hub with modular SpokesFully isolated markets + vault curators
Liquidity modelShared pool, risk segmented by SpokePer-market pools, composed by vaults
GovernanceAAVE token holders set Hub and Spoke parametersPermissionless market creation, curator-managed vaults
Market share (DeFi lending)~50% of lending TVL~10% and growing (27% month-over-month TVL growth in Q1 2026)
TVL (combined)$15 to 18 billion across 20+ chains$10+ billion, primarily Ethereum and Base
Rate efficiencyRates reflect aggregate supply/demand across SpokesRates reflect concentrated demand per isolated market
Risk customizationGovernance-controlled per SpokePermissionless per market, curator-controlled per vault
Cross-chainCCLL planned via Chainlink CCIPNo native cross-chain layer

Other Competitors

Beyond Morpho, Aave faces competition from specialized protocols across the lending stack. Compound continues to operate a simpler pooled model. Euler v2 introduced modular vaults with a governance-minimized design. Spark Protocol (MakerDAO's lending arm, distinct from Spark the Bitcoin Layer 2) operates a forked Aave v3 instance tuned for DAI borrowing. Each represents a different point on the tradeoff between composability, capital efficiency, and governance overhead.

Security Considerations

The Hub-and-Spoke architecture introduces a multi-layer system that is more complex than v3's monolithic pools. This complexity carries security implications.

Hub-Level Risk

A vulnerability in the Hub contract affects every Spoke connected to it. In v3, an exploit in one pool left other pools untouched. In v4, the Hub is a single point of shared state. Aave mitigates this through conservative initial caps (limits are raised gradually as live usage is observed) and formal verification of Hub contracts.

Spoke Isolation Guarantees

Spoke-level risk isolation depends on correctly enforced credit lines. If a Spoke can overdraw from the Hub beyond its credit line, bad debt in one market could infect the shared pool. The LlamaRisk analysis of the launch parameters notes that spoke launches are intentionally slow until stress testing validates the isolation model under real market conditions.

Oracle Dependencies

Aave v3 experienced an oracle misconfiguration in March 2026 that caused approximately $862,000 in losses. As v4 adds cross-chain oracle coordination to its design, the attack surface for oracle manipulation grows. Each Hub needs consistent, timely price data, and the CCLL will require cross-chain oracle agreement for positions that span multiple networks.

TVL and Market Position

Aave remains the largest DeFi lending protocol by a significant margin. Combined TVL across all versions and chains sits between $15 and $18 billion as of late 2026, with Ethereum mainnet holding approximately 83% of the total. The protocol handles roughly 50% of all active DeFi loans.

The transition from v3 to v4 is happening gradually. The initial Ethereum deployment launched with conservative caps, and governance votes are progressively raising limits as the system proves stable under load. Aave v4 has also deployed on Avalanche with a focus on institutional real-world asset (RWA) markets, signaling that the Hub-and-Spoke model enables specialized deployments that v3's monolithic pools could not support cleanly.

Revenue dynamics are also shifting. The sustainable revenue question facing DeFi protocols is particularly acute in lending, where protocol fees must balance between attracting suppliers (who want higher yields) and borrowers (who want lower rates). Aave's v4 liquidation engine, with its tunable per-Spoke parameters, gives governance finer control over this balance than v3's one-size-fits-all approach.

What Unified Liquidity Means for the Broader Ecosystem

Aave v4's unified liquidity thesis addresses a problem that extends well beyond DeFi lending. Any protocol that deploys across multiple chains faces the same fragmentation challenge: how to maintain deep, efficient markets without forcing users to manually bridge assets and hunt for the best venue.

In the payments and infrastructure domain, this same challenge manifests differently. Spark, for example, solves a parallel fragmentation problem for Bitcoin: rather than requiring users to manage Lightning channels, bridge between layers, or choose which chain to hold funds on, Spark provides a unified experience where Bitcoin and stablecoins move instantly without users needing to understand the underlying layer topology. The design philosophy is similar: abstract away the complexity of multi-layer coordination so that users interact with a single, coherent system.

For developers building on these platforms, the Spark SDK offers an example of how unified liquidity design translates into developer experience: a single API for Bitcoin and stablecoin transfers that works across layers without requiring the application to manage routing or bridging logic.

What to Watch

Several developments will determine whether Aave v4's unified liquidity thesis succeeds:

  • CCLL rollout timeline: the cross-chain layer is the missing piece that turns per-network unification into true protocol-wide liquidity. Delays or security incidents in Chainlink CCIP could push this out further
  • v3 to v4 migration velocity: how quickly existing deposits move from v3 pools to v4 Hubs will determine whether the protocol actually achieves unified liquidity or simply adds another fragmented deployment
  • GHO adoption: if GHO does not achieve meaningful circulating supply beyond its current range, its role as the cross-chain settlement layer becomes less compelling than simply bridging USDC
  • Morpho and modular competitor growth: if isolated market models continue gaining share, it validates the thesis that capital efficiency matters less than risk customization for sophisticated users
  • Hub security under stress: the first major market downturn after v4 launch will test whether the Hub-and-Spoke isolation model holds under real liquidation pressure

The AAVE governance token holders approved the v4 activation unanimously in March 2026, with over 645,000 AAVE cast in favor. That level of consensus reflects confidence in the design, but the real test is live market performance over the coming year.

For a deeper look at how cross-chain coordination is evolving across the ecosystem, see our coverage of ERC-7683 cross-chain intents and the broader L2 liquidity fragmentation problem.

This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.