Skip to content
Blockchain Posts

protocol

Aave V4 goes live on Avalanche with hub-and-spoke, first V4 chain beyond Ethereum

Aave activated V4 on Avalanche on July 15 with one Liquidity Hub, three Spokes and a $15M Avalanche Foundation milestone-based incentive envelope.

by 6 min read
defiprotocolaaveavalancheethereum

Aave activated V4 on Avalanche on July 15, 2026, the first deployment of the fourth-generation lending protocol outside Ethereum mainnet. The rollout is structured around Aave's new hub-and-spoke architecture — one shared Core Liquidity Hub feeding three specialised markets ("Spokes") — and comes with an Avalanche Foundation commitment of up to $15 million in milestone-based incentives. Primary reference is the Aave blog and Aave Labs' launch statement; independent write-ups on the Avalanche activation include Crypto Briefing, crypto.news, and The Crypto Times.

What happened

V4 launched on Ethereum mainnet on March 30, 2026, announced at EthCC in Cannes with Lido, EtherFi, Kelp, Ethena and Lombard as initial Spoke operators. Between then and July 15, V4 stayed Ethereum-only while Avalanche continued to host Aave V3. On July 15 that changes: V4 is now live on Avalanche in parallel with the existing V3 deployment, with a controlled-launch posture — conservative supply and borrow caps, DAO-managed cap expansions, and additional Spokes added only after the first ones prove out.

Aave Labs' framing is that V3 has run on Avalanche since 2022 without a serious incident — through liquidations, oracle updates and stressed markets — which is why Avalanche is the first non-Ethereum home for V4 rather than an L2 like Arbitrum, Base or Optimism. Those are expected next, but explicitly gated on Avalanche's V4 stability metrics this quarter.

Mechanism — one Hub, three Spokes

V4's design separates the shared liquidity pool from the lending markets built on top of it. The Hub holds capital centrally. Each Spoke connects to the Hub with its own collateral list, risk parameters, oracle setup and liquidation rules, so distinct lending environments can share one pool of liquidity without cross-contaminating each other's risk. On Ethereum, that structure was used to isolate LST/LRT Spokes (Lido, EtherFi, Kelp, Ethena) from base markets; on Avalanche it opens the door to RWA and forex Spokes.

The initial Avalanche configuration:

  • 1 Liquidity Hub — the shared capital pool.
  • 3 Spokes:
    • Main Market — general-purpose lending on core assets.
    • AVAX Correlated Market — LST-style AVAX exposure isolated from the main pool.
    • Forex Market — a Spoke tuned for stable-to-stable and multi-currency pairs, including EURC.

Supported Hub collateral at launch: AVAX, sAVAX, BTC.b, WETH.e, USDC, USDT, EURC. Under this structure, a future RWA Spoke — Aave has flagged tokenised US Treasuries, money-market funds, private credit and corporate bonds as targets — plugs into the same Hub without a separate liquidity migration.

Numbers block

- Chain                     : Avalanche C-Chain
- Protocol version          : Aave V4
- Deployment date           : 2026-07-15
- Prior V4 deployment       : Ethereum mainnet (2026-03-30, EthCC Cannes)
- Architecture              : one Core Liquidity Hub + three Spokes
- Initial Spokes            : Main Market, AVAX Correlated Market, Forex Market
- Hub collateral at launch  : AVAX, sAVAX, BTC.b, WETH.e, USDC, USDT, EURC
- Incentive envelope        : up to $15,000,000 committed by Avalanche
                              Foundation, milestone-based (tied to new Hub
                              launches + market growth benchmarks)
- Next targets              : Arbitrum, Base, Optimism — sequenced on
                              Avalanche V4 stability metrics this quarter
- Planned future Spokes     : RWA Hub for tokenised US Treasuries, money-
                              market funds, private credit, corporate bonds
- Governance                : Aave DAO controls cap expansions and new
                              Spoke additions

Impact

For Aave, this is the moment V4 stops being an Ethereum-only story. The Ethereum mainnet deployment proved the architecture; Avalanche is where the multi-chain thesis begins to be tested against a live market that has already carried V3 through cycles. If V4 holds up over the next quarter, the queued L2 rollouts (Arbitrum, Base, Optimism) become mechanical rather than experimental.

For Avalanche, the $15M milestone envelope is the more meaningful part. Milestone-based means the money moves as Hubs launch and specific market-growth thresholds hit — not upfront, not proportional to TVL, not paid to headline lenders regardless of stickiness. That's the shape of incentive program the DeFi post-mortem literature has been arguing for since the 2021 mercenary-liquidity wave. Whether it produces stickier TVL than V3 saw on the same chain is the question the next 90 days answers.

The RWA angle is where the story reaches beyond DeFi. A Spoke architecture that can host tokenised Treasuries or MMF collateral behind a compliant permissioning layer while sharing liquidity with the retail Hub is exactly the shape institutions have said they want. Aave has flagged the RWA Hub as a proposal, not a launch — an important distinction until an ARFC and on-chain vote actually pass.

Action checklist

  1. Suppliers on Aave V3 Avalanche — no forced migration. V3 continues to run in parallel. V4 supply/borrow caps at launch are deliberately conservative; expect modest yields until DAO governance raises them.
  2. Delegates and risk stewards — track the ARFC and Snapshot cadence for the RWA Hub proposal. That vote is where the institutional-collateral thesis is decided in public.
  3. Protocol integrators using Aave through routers or leverage vaults — verify that your integration reads the correct Hub reserve list and doesn't hardcode V3 pool addresses. Hub/Spoke split means the code-path branching is not the same as the V3-to-V3 pattern.
  4. Auditors and risk teams looking at V4 code paths — the third-party audit set for the V4 codebase (Pashov, Sherlock, Certora, MixBytes, Savant, Enigma) was completed for v3.7 in March 2026; the Avalanche activation reuses that audit surface. Any Avalanche-specific parameter divergences from Ethereum V4 belong under separate review.

Context — the hub-and-spoke wager, in a chain-by-chain build-out

Aave's V4 architecture is a specific answer to a specific problem: V3 had 10+ chain deployments (Ethereum, Polygon, Arbitrum, Optimism, Avalanche, Base, BNB, Scroll, zkSync, Gnosis, Metis) each with its own reserve list and its own risk parameters, which meant risk configuration was duplicated, upgrades were plural, and every new asset onboarding was a per-chain governance load. Hub-and-Spoke consolidates capital while letting risk fragment — the opposite of V3's per-market silos.

The Avalanche launch is the earliest read on whether that architecture works outside a single chain. Two months ago Aave Labs was still fighting a governance rift — the Aave Chan Initiative announced in early March that it would exit the DAO by July, following BGD Labs' April wind-down. The service-provider layer that scaled V3 governance is thinner than it was; V4's rollout has to prove that a leaner governance stack can still ship multi-chain deployments on schedule. July 15 is the first data point.

The next reads: the Arbitrum, Base and Optimism deployments (order of L2 rollout not committed), whether the RWA Hub proposal actually reaches on-chain vote in Q3, and how much of the $15M Avalanche envelope gets released as milestones hit.

Sources:

Related stories