Title: [ARFC] Aave DAO Policy Change: Halt Listings on all Aave v1 & v2 Non Permissioned Deployments
Author: @Llamaxyz, Gauntlet, Chaos Labs, 3SE Holdings & @ItsFreeRealEstate
As part of the Sunsetting of v1, the v2 → v3 Migration & the Deprecation of v2 discussions being conducted by the community here and here, the authors are appealing to the Aave DAO to adopt a policy of halting listings on the following markets:
- Aave v1 (Ethereum & Uniswap Markets)
- Aave v2 (Ethereum, AMM, Polygon & Avalanche Markets)
With the release of Aave v3 featuring superior risk management parameters and controls, this proposal advocates only enabling future asset listings to occur on Aave v3 deployments. Upon implementation of this upgrade, via a successful Snapshot vote, assets can no longer be add/introduced to the Aave v2 deployments.
Note: The Aave ARC & Centrifuge RWA markets, which are powered by the “Permissioned” V2 codebase are not included. These liquidity pools support the latest battletested version of the “Permissioned” code base.
This proposal seeks to begin the transition from v2 to v3 deployments. The first step in this progression is to focus our efforts on growing the v3 deployments whilst continuing to actively support the v2 deployments in all other areas. Going forward all future asset listings are to be limited to only v3 deployments.
Successful passing of this ARFC will indicate the DAO has decided that the various V3 deployments are the future of the Aave DAO, and support of the various listed markets will be limited to Risk and Critical Technical Updates.
The Aave Community upon successfully voting on Snapshot to implement this upgrade, will prevent any further assets from being added to any of the following Aave Market pools, as identified by their LendingPool Addresses.
- Ethereum V1 Market 0x398eC7346DcD622eDc5ae82352F02bE94C62d119
- Ethereum V1 Uniswap Market 0x2F60C3EB259D63dcCa81fDE7Eaa216D9983D7C60
- Ethereum V2 Market 0x7d2768de32b0b80b7a3454c06bdac94a69ddc7a9
- Ethereum V2 AMM Market 0x7937d4799803fbbe595ed57278bc4ca21f3bffcb
- Polygon V2 Market 0x8dff5e27ea6b7ac08ebfdf9eb090f32ee9a30fcf
- Avalanche V2 Market 0x4F01AeD16D97E3aB5ab2B501154DC9bb0F1A5A2C
This represents the first progression toward deprecating the v1 & v2 deployments across all networks.
Criteria for a success Snapshot vote, the Short Executor criteria must be met:
Reference: AIPs - Governance
A Snapshot will be created on the 30th November with the vote commencing on the 1st December.
Copyright and related rights waived via CC0.