Aave DAO officially initiates the V4 upgrade community discussion process through the ARFC proposal

AAVE2,29%
GHO-0,16%

Gate News, March 23 — Aave DAO has approved a proposal via the Aave Request for Comment (ARFC) voting, officially initiating community discussions for the deployment of Aave V4. The proposal received 100% support on the governance platform, marking a key step forward in the protocol’s major upgrade. The ARFC is in a non-binding phase, aimed at gathering community feedback and refining the plan. It will later proceed to an official on-chain Aave Improvement Proposal (AIP) vote and mainnet deployment, expected to be completed this year.

This upgrade will introduce a new Hub and Spoke architecture, integrating liquidity through a unified Liquidity Hub. Multiple Spoke modules will define different lending rules, risk parameters, and collateral strategies, enhancing capital efficiency and enabling more granular risk isolation. Additionally, V4 will address liquidity fragmentation issues in the current protocol, support more diverse market structures, strengthen native stablecoin GHO integration, and upgrade the liquidation mechanism. Aave states that this architecture will evolve the protocol from a single lending model into a more flexible on-chain financial infrastructure, improving liquidity depth and risk pricing capabilities.

View Original
Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments