Aave sets v3-to-v4 timeline as BGD Labs plans exit

What to Know:

• Aave v3 continues short-term; migration to v4 will be phased.
• Timelines subject to on-chain governance; adjustments as development milestones completed.

Aave has clarified how it will transition from v3 to v4, stating that v3 will continue to operate normally in the short term. According to Aave DAO governance updates, the migration is planned as a phased process rather than an immediate cutover.

The approach prioritizes operational continuity for users and integrators while v4 development proceeds. Timelines remain subject to on-chain governance and may be adjusted as milestones are met.

In practice, v3 remains the primary production system until v4 is ready, with ongoing maintenance and risk parameter management. Feature innovation is expected to concentrate on v4 once it launches.

What v3 normal operation means for users and integrators now

For users, core functions on v3, supplying, borrowing, repaying, and withdrawing, continue as normal. Critical security patches and parameter updates are expected to be maintained during this phase.

Once v4 launches, migration is described as voluntary, and withdrawals on v3 remain open. No forced deprecations or lockups are indicated in the current plan.

For integrators, existing v3 endpoints and documentation are expected to remain available, supporting parallel operations while v4 adoption ramps. Over time, risk settings and incentives may diverge by version as governance calibrates markets.

At the time of writing, AAVE traded near $123.57 with an RSI around 40.51 and approximately 13.14% volatility, based on data from the market metrics provided. These figures are contextual and do not imply any forecast.

Aave Will Win Framework: three-phase migration overview

According to Aave Labs’ February 2026 Temp Check, the “Aave Will Win Framework” outlines a three-phase transition. During Active Development, v3 remains the primary production system, receiving maintenance and risk updates while v4 finishes development.

Upon v4 launch, the plan enters Stable Maintenance, shifting new feature work to v4 while preserving full user access and documentation on v3. Migrations are voluntary in this phase.

Roughly 8–12 months after v4 launch, the framework envisions Legacy Support, with gradual parameter changes to encourage migration while keeping v3 withdrawals open indefinitely. Governance would limit v3 changes to critical security matters.

“BGD Labs, a core service provider to Aave DAO, described v3 as in a ‘very solid and future‑proof state’ and called proposals to intentionally degrade v3 ‘borderline outrageous’ in a February 2026 governance post, adding that its service contributions are scheduled to cease after April 1, 2026 with continuity maintained through that date.”