Aave

Simple Summary

This proposal will perform the next step in sunsetting Aave v1 by freezing all reserves on the Aave Ethereum v1 and Aave Ethereum Amm V1 pool.

Motivation

Aave V1 was deployed on the Ethereum network back in January 2020, being the first step of everything that would come afterward on the Aave ecosystem. Since then, countless developments happened in the community, amongst them, 2 more iterations of the protocol: Aave v2 and Aave v3. After the deployment of Aave v2 Ethereum, almost 2 years ago (December 2020), the general approach of the community was to progressively sunset Aave v1, with steps like enabling a migration tool v1 → v2 and disabling stable borrowing on v1 (more information here). Therefore the next step that was decided upon in this snapshot vote is to freeze all the v1 reserves. With this change in place, users can still repay & withdraw, but no longer supply and borrow.

Specification

The proposal fetches the LendingPoolCore and LendingPoolConfigurator from the respective Aave ethereum and Aave ethereum amm LendingPoolAddressesProviders via getLendingPoolCore() & getLendingPoolConfigurator(). As the next step it fetches all reserves via lendingPoolCore.getReserves() and freezes them one by one, by iterating though the list and calling lendingPoolConfigurator.freezeReserve(reserve).

References

• Deployed implementation
• E2E test suite
• ProposalPayloadAaveFreezeV1
• Original discussion
• Related discussion

Copyright

Copyright and related rights waived via CC0.