Aave v2 non-Ethereum pools next deprecation steps
01Summary
Proposal to freeze all remaining unfrozen assets in Aave v2 pools on Polygon and Avalanche to accelerate deprecation. Users can still withdraw, repay debt, and migrate to v3. This reduces monitoring overhead while being non-invasive.
- Type
- protocol deprecation
Key changes
- Freeze DAI, USDC, USDT, WBTC, WETH, WPOL on Aave v2 Polygon(high)
- Freeze DAI.e, USDC.e, USDT.e, WETH.e, WAVAX on Aave v2 Avalanche(high)
- Users retain ability to repay debt, withdraw assets, and process liquidations on frozen pools(medium)
Notable concerns
- Aave v2 Ethereum pool remains unfrozen due to larger outstanding pool size
- Freezing assets creates non-invasive deprecation but removes ability to supply new assets to these pools
Generated by Kvorum
02Description
Simple Summary
Proposal to progress on the deprecation of the lowest-size Aave v2 pools (Polygon and Avalanche v2), by freezing all the assets, not allowing more growth on both pools, while same time being non-invasive for users (they can withdraw, repay, and migrate to v3).
Motivation
All Aave v2 instances (Ethereum, Polygon, Avalanche) have undergone a process of continuous deprecation in favour of v3 during the last years, and for the last months, the non-Ethereum instances sit at low deposits, but with some of the assets unfrozen.
Keeping those v2 legacy pools in this stage is not ideal, as it creates monitoring overhead for all contributors, both on the risk and technical side.
So while on the Aave v2 Ethereum pool we think the outstanding pool size still points to waiting more time for a full freeze, we believe for v2 Polygon and Avalanche is fully reasonable to proceed.
Specification
The on-chain AIP will call freezeReserve(asset) on the LendingPoolConfigurator of both Polygon and Avalanche v2 on all currently non-frozen assets.
- Assets frozen on Polygon V2:
DAI,USDC,USDT,WBTC,WETH,WPOL - Assets frozen on Avalanche V2:
DAI.e,USDC.e,USDT.e,WETH.e,WAVAX
As previously commented, this is a non-invasive action, as liquidations will still be processable, and users will be able to repay their debt, withdraw assets, and consequently migrate to the v3 instances on each network.
References
- Implementation: AaveV2Polygon, AaveV2Avalanche
- Tests: AaveV2Polygon, AaveV2Avalanche
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
A calldata-vs-description analysis is not generated yet. Review the decoded actions →
04Actions
This proposal carries no on-chain actions.
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedTemporary Freeze of Long-Tail V2 Assets80%
- aaveexecutedChaos Labs V2 to V3 Migration Next Steps80%
- aaveexecutedAllow Emergency Admin to freeze on Aave V279%
- aavedefeatedFreeze Aave V179%
- aaveexecutedFreeze Aave V179%
- aaveexecutedDeprecate Aave V2 AMM Market78%
- aaveexecutedDisable Stable Borrows78%
- aavedefeatedRisk Parameter Updates for Aave v2 Polygon76%
- aaveexecutedFreeze and set LTV to 0 for DPI, BAL, CRV, and SUSHI on Aave v3 Polygon, 2024.01.1975%
- aaveexecutedFreeze TUSD Reserve on Aave V2 Ethereum75%