Deep Dive
1. V4 Codebase Freeze & Security Push (February 2026)
Overview: Aave Labs released version v0.5.9 and froze the V4 codebase, restricting changes to only security-related fixes. This stabilizes the code for final, intensive security reviews before mainnet launch.
The development team published three audit reports from leading firms, which confirmed zero high or critical severity findings. A public bug bounty contest on Sherlock also concluded with over 900 participants and no major vulnerabilities reported. The focus has shifted to finalizing the "Hub-and-Spokes" launch configuration with risk management partners.
What this means: This is bullish for AAVE because it demonstrates a rigorous, security-first approach to the largest protocol upgrade in years. A clean audit record reduces the risk of exploits and builds trust for users and institutions planning to use the new system.
(Source)
2. V3.6 Introduces Liquid eMode & Optimizations (9 January 2026)
Overview: This update introduced "Liquid eMode," a feature that allows assets to be listed in multiple efficiency modes with exclusive collateral and borrowing rules. It also added renounce allowance functionality and gas optimizations.
The upgrade was initially deployed on nine networks including Sonic, Optimism, and Ethereum, expanding Aave's reach and efficiency for users on those chains.
What this means: This is neutral to bullish for AAVE. For users, it means more flexible borrowing options and potentially lower transaction costs. The multi-chain deployment strengthens Aave's presence, but as a incremental update to V3, its impact is less transformative than the upcoming V4.
(Source)
3. Major V4 Development & Security Review Phase (August 2025)
Overview: The core development work for Aave V4 was completed, including a major code refactor and performance optimizations. The team transitioned the codebase to a stable state and initiated security reviews with multiple external audit firms.
Concurrently, the team launched Aave Horizon, a new market for real-world asset (RWA) collateral, and released a full developer toolkit (SDK and API) for the V3 protocol.
What this means: This is bullish for AAVE because it marked a pivotal shift from research to actionable, auditable code for V4. The parallel launch of Horizon and developer tools shows a strategy to grow the ecosystem now while building its future foundation, which could attract more institutional and developer activity.
(Source)
Conclusion
Aave's development trajectory is firmly fixed on launching its modular V4 architecture, with recent codebase activity dominated by security hardening and final pre-launch preparations. The protocol continues to iterate on its current V3 deployment with feature updates, ensuring continued utility during the transition. How smoothly will the community and liquidity migrate from V3 to the new V4 hubs?