Strategy on sunset of Aave v1

Summary

Decide an strategy to sunset Aave v1 Ethereum and Aave v1 AMM, given the existence for a long time already of v2 and v3 versions of the Aave liquidity protocol.

Context

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 https://governance.aave.com/t/aave-protocol-v1-v2-migration-tool-and-transition-plan/2053 2)

Options proposed

• Freezing (disable additive actions). Probably the natural one, to reduce any kind of overhead from the community going forward.
• Disable variable borrowing. Less aggressive, with the plan to follow up with another to freeze the pools.
• Do nothing. Keep v1 as it is, just waiting for everybody to exit the pool, and nobody entering.