Greetings, Aave Community,
Intro
The V2 interface is to move off the main Aave app into a dedicated legacy interface, preserving access for users with open positions while removing V2 conditionals from the core SDK and frontend. The change consolidates the active surface of Aave around V3 and V4. This step closes one chapter of the protocol and sets the stage for the next.
Rationale
Over the past years, Aave V2 has been a major chapter in the protocol’s evolution, powering billions in liquidity and establishing the foundation for the protocol’s global reach. With the successful deployment and adoption of V3, and now the introduction of the V4 Hub & Spoke architecture, the time has come to formally transition V2 into legacy mode in the Aave Interface.
Maintaining V2 inside the primary interface creates unnecessary engineering overhead: each new feature or SDK update must account for outdated branches and edge cases, slowing iteration and raising the risk of regressions. It also creates UX ambiguity for new users, who encounter a version of the protocol that no longer reflects Aave’s current risk frameworks or product direction.
Plan
Similar to the establishment of the standalone Aave V1 interface, The main Aave interface will redirect V2 traffic to a standalone instance, at https://v2-market.aave.com/ for the duration of its wind-down. This ensures repay, withdraw, and migrate flows remain available while decoupling legacy UX from the primary app. The transition is sequenced:
-
Redirect users to the legacy interface
-
Maintain continuity for position management
-
Progressively phase down visibility as the DAO continues to deprecate V2.