• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Event HorizonEvent Horizonby0xFAD69Bd739c64cC8e3f1C3bb3B60fe4f160174Cchvax.eth

[AAVE] Aave v2 non-Ethereum pools next deprecation steps

Voting ended 9 months agoSucceeded

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.

https://app.aave.com/governance/v3/proposal/?proposalId=333

Off-Chain Vote

YAE
219 HVAXVC100%
NAY
0 HVAXVC0%
Quorum:21900%
Download mobile app to vote

Discussion

Event Horizon[AAVE] Aave v2 non-Ethereum pools next deprecation steps

Timeline

Jun 26, 2025Proposal created
Jun 27, 2025Proposal vote started
Jun 29, 2025Proposal vote ended
Mar 17, 2026Proposal updated