Aave V4 Explained: How Hubs, Spokes, and Credit Lines Redefine DeFi Liquidity Management

TLDR:

• Aave V4 uses immutable Liquidity Hubs to hold assets and track supplied and borrowed balances across markets.
• Spokes handle all user-facing functions like supplying and borrowing, and can be upgraded without changing Hub code.
• Credit lines connect each Spoke to a Hub on a per-asset basis, with draw caps enforced on every transaction.
• Governance controls liquidity access by adjusting draw caps per asset, giving the Aave DAO precise risk management tools.

Aave V4 brings a restructured liquidity model built around three core components: Hubs, Spokes, and credit lines. Understanding how these three parts connect explains how liquidity moves across the protocol.

It also shows how risk is managed across different markets. This architecture marks a clear shift from previous Aave versions.

For anyone following DeFi closely, the design choices behind V4 reflect a more deliberate approach to building modular, upgradeable lending infrastructure.

What Liquidity Hubs and Spokes Are Designed to Do

A Liquidity Hub in Aave V4 is a smart contract that holds deposited assets. When a user supplies USDC, those tokens are stored directly inside a Hub.

Each Hub tracks how much of every asset has been supplied and how much has been borrowed across all connected markets.

As crypto researcher @0xKolten explained, Hubs are intentionally immutable, meaning their underlying code cannot be modified after deployment.

This keeps the liquidity layer stable over time, reducing the risk of bugs introduced through upgrades. New assets can still be registered through governance, since adding an asset is treated as a state change, not a code change.

A single blockchain network can support multiple Hubs, each running its own independent balance sheet. The current Ethereum deployment launched with three: Core Hub, Prime Hub, and Plus Hub. None of these Hubs share accounting with one another.

Spokes are the contracts users interact with directly. Supplying, borrowing, repaying, and withdrawing all happen through a Spoke.

Each Spoke carries its own market logic, including collateral factors, price feeds, and liquidation rules. Because Spokes are upgradeable, governance can adjust risk parameters without affecting the Hub layer.

How Credit Lines Tie the Entire System Together

Every connection between a Spoke and a Hub is a credit line, and each one is defined per asset. A Spoke borrowing USDC from a Hub and that same Spoke borrowing USDT from the same Hub are two entirely separate credit lines. Each carries its own draw cap, which the Hub enforces before any transaction is processed.

The draw cap works similarly to a borrow cap in Aave V3. Governance can raise it to open more access or lower it to reduce the Spoke’s exposure. Setting a cap to zero stops new borrowing entirely while keeping all existing positions intact.

A Spoke can hold credit lines to more than one Hub simultaneously. The Bluechip Spoke on Prime Hub demonstrates this.

Users supply WETH, wstETH, WBTC, and cbBTC as collateral into Prime Hub, while that same Spoke holds separate credit lines to Core Hub for stablecoins like USDC, USDT, and EURC.

When a borrower draws stablecoins through the Bluechip Spoke, the liquidity comes from Core Hub up to each asset’s authorized cap.

The tokens received are the actual underlying assets, not synthetic versions. This structure gives Aave governance a direct, asset-level tool to control how much of any Hub’s liquidity a Spoke can access at any given time.

The post Aave V4 Explained: How Hubs, Spokes, and Credit Lines Redefine DeFi Liquidity Management appeared first on Blockonomi.