Aave V3 will remain operational as V4 launches in a phased manner.

iconKuCoinFlash
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
Aave V3 will remain fully operational as the protocol transitions to Aave V4 through a phased rollout. Aave Labs team member Kolten confirmed on X that V3 will not be immediately replaced and migration will not be rushed. The protocol update, built on years of development, will gradually introduce deposit limits and expand collateral types. On-chain updates show that Aave continues to support V3 while advancing V4.

Odaily Planet Daily report: Aave Labs team member Kolten posted on X, stating that there has been some confusion regarding the timeline for the transition from Aave V3 to Aave V4. He clarified that Aave V3 will continue to operate normally for the foreseeable future and will not be immediately replaced upon the launch of Aave V4; there are currently no plans to accelerate the migration.

Kolten stated that Aave V4 is built on nearly a decade of protocol development and business partnership experience, and its mainnet launch will follow a cautious, phased approach, including initial limits on deposit sizes and gradual expansion of collateral types and use cases. Over the past year, Aave Labs has continued advancing the V3 ecosystem and has not slowed these efforts despite the upcoming release of V4.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.