# Aave v4 launched on Ethereum with Hub-and-Spoke liquidity architecture

> The launch created a live lending exposure in which Hubs custody shared liquidity while Spokes define collateral, risk-premium, and liquidation rules. Advisor analysis must therefore identify the exact Hub, Spoke, and asset rather than inherit an Aave-wide conclusion.

- URL: https://riadefi.com/on-chain/2026-03-30-aave-v4-ethereum-mainnet-launch/
- Type: Launch or access
- Stage: Live launch
- Evidence: confirmed
- Materiality: material
- Event date: 2026-03-30
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Advisor-relevant: no
- Affects: Aave v4 (protocol)

## What happened

Aave v4 became live on Ethereum mainnet with three Liquidity Hubs, multiple Spokes, conservative initial caps, and the Aave Pro interface.

## What changed

The launch created a live lending exposure in which Hubs custody shared liquidity while Spokes define collateral, risk-premium, and liquidation rules. Advisor analysis must therefore identify the exact Hub, Spoke, and asset rather than inherit an Aave-wide conclusion.

## What did not change

Aave v3 remained a separate protocol architecture and no migration of existing v3 positions was established. The launch, audits, conservative caps, and Aave branding did not make v4 approved or suitable for client allocation. This March event does not establish an Avalanche launch.

## Confirmed

- Aave v4 was live on Ethereum mainnet on March 30, 2026.
- The initial deployment contained Core, Prime, and Plus Liquidity Hubs.
- Spokes drew from shared Hub liquidity while retaining distinct collateral and risk rules.
- Initial supply and borrow caps were intentionally conservative.
- Aave Pro provided a live interface for supplying and borrowing through v4.

## Still open

- Production behavior under large liquidations, high utilization, credit-line contraction, and Spoke upgrades was not yet demonstrated.
- Exact loss boundaries and withdrawal exposure across every connected Hub and Spoke required separate diligence.
- No evidence established that any Ketju mandate approved Aave v4 at launch.

## What it means for an advisor

- Create or review a separate aave-v4 memo; do not extend the aave-v3 approval to v4.
- Require proposed exposure to identify the exact chain, Hub, supplying Spoke, asset, caps, credit lines, pause authority, and liquidation configuration.
- Maintain zero allocation until the maturity and reproducibility requirements in the Aave v4 diligence file are independently satisfied.

## Sources

1. [Aave V4 is Live on Ethereum](https://aave.com/blog/aave-v4-live-ethereum) · Aave Labs · 2026-03-30


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.