The Aave v4 upgrade, coming in Q4 2025, introduces a Hub-and-Spoke architecture, a Reinvestment Module to deploy idle liquidity into low-risk strategies, and a new liquidation engine—designed to boost protocol liquidity, reduce gas costs, and improve UX for lenders and borrowers.
Aave v4 adds a Reinvestment Module to turn idle pool float into yield.
Hub-and-Spoke architecture aims to reduce gas and centralize protocol logic.
The upgrade includes a redesigned liquidation engine and UX improvements, per the Sept. 15 roadmap.
Aave v4 upgrade: Reinvestment Module, Hub-and-Spoke and liquidation engine explained — read the roadmap highlights and implications for liquidity. Learn more now.
‘,
‘
🚀 Advanced Trading Tools Await You!
Maximize your potential. Join now and start trading!
‘,
‘
📈 Professional Trading Platform
Leverage advanced tools and a wide range of coins to boost your investments. Sign up now!
‘
];
var adplace = document.getElementById(“ads-bitget”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBitget”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBitget.length) : sessperindex;
adplace.innerHTML = adscodesBitget[adsindex];
sessperindex = adsindex === adscodesBitget.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBitget”, sessperindex);
}
})();
What is the Aave v4 upgrade?
The Aave v4 upgrade is a protocol-level release scheduled for Q4 2025 that introduces a Hub-and-Spoke architecture, a Reinvestment Module, UX overhauls and a new liquidation engine. The upgrade aims to improve liquidity efficiency, reduce transaction gas, and increase yield on idle capital.
How does the Reinvestment Module work?
The Reinvestment Module allows Aave to allocate unused pool float into low-risk, highly liquid yield strategies while keeping funds available for withdrawals. The module is designed to earn incremental yield for liquidity providers without compromising capital safety.
According to the Aave Sept. 15 roadmap, the module will use on-chain, permissionless strategies that prioritize liquidity and low volatility. Implementation details show native integration with pool accounting to preserve user balances and withdrawal guarantees.
Why is Hub-and-Spoke architecture important?
Hub-and-Spoke centralizes shared protocol logic in a “Hub” while deploying smaller “Spokes” for individual markets. This design reduces redundant code, lowers gas costs per market, and simplifies upgrades. For Aave, the architecture is expected to scale new markets faster and streamline governance updates.
‘,
‘
🔒 Secure and Fast Transactions
Diversify your investments with a wide range of coins. Join now!
‘,
‘
💎 The Easiest Way to Invest in Crypto
Dont wait to get started. Click now and discover the advantages!
‘
];
var adplace = document.getElementById(“ads-binance”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBinance”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBinance.length) : sessperindex;
adplace.innerHTML = adscodesBinance[adsindex];
sessperindex = adsindex === adscodesBinance.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBinance”, sessperindex);
}
})();
The Aave development team published a V4 Development Update on Sept. 15, 2025, outlining the timeline and current progress. The roadmap clarifies development milestones, testing phases, and planned mainnet deployment windows for Q4 2025.
Aave v4’s new liquidation engine focuses on execution efficiency and reduced slippage during liquidations. The engine refines auction mechanics and aims to lower costs for liquidators while protecting borrower solvency. Expect faster resolution times and tighter cost controls compared with previous versions.
Front-loaded benefits include higher effective yields for liquidity providers via the Reinvestment Module, lower gas per interaction due to architectural improvements, and smoother UX during borrowing and lending flows. These changes target efficiency gains without introducing speculative leverage risks.
‘
];
var adplace = document.getElementById(“ads-htx”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexHtx”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesHtx.length) : sessperindex;
adplace.innerHTML = adscodesHtx[adsindex];
sessperindex = adsindex === adscodesHtx.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexHtx”, sessperindex);
}
})();