Approve further steps of Aave v1 off-boarding, to reduce operational overhead on deprecated Aave instances.
The Aave protocol v1 was released in January 2020 and eventually superseded by Aave protocol v2 in December on the same year.
While Aave v1 has been deprecated for a long time, some liquidity is still stuck on the protocol 1. Even if this instance is not covered by the Aave Safety Module, being part of Aave, it still is monitored and evaluated whenever development and/or security decisions are made.
This creates meaningful overhead for all involved development & security teams, which directly adds cost to the Aave DAO. Additionally, the architecture of Aave v1 is quite different to Aave v2 & v3, making it the most ad-hoc instance of Aave.
On 6th of february a first set of measures was implemented by the DAO to accelerate the offboarding process, followed by a second proposal on 3th of march.
This Phase 3 is the final phase of the off-boarding as suggested on the forum with some slight modifications:
Upon execution the proposal upgrades the following contracts:
Also, the proposal will change the pool configuration:
Copyright and related rights waived via CC0.