Aave V1 Deprecation Phase 3














Aave V1 Deprecation Phase 3







Author

BGD Labs @bgdlabs

Creator

0xf71fc92e2949ccF6A5Fd369a0b402ba80Bc61E02

Simple Summary

Approve further steps of Aave v1 off-boarding, to reduce operational overhead on deprecated Aave instances.

Motivation

The Aave protocol v1 was released in January 2020 and eventually superseded by Aave protocol v2 in December on the same year.

While Aave v1 has been deprecated for a long time, some liquidity is still stuck on the protocol 1. Even if this instance is not covered by the Aave Safety Module, being part of Aave, it still is monitored and evaluated whenever development and/or security decisions are made.

This creates meaningful overhead for all involved development & security teams, which directly adds cost to the Aave DAO. Additionally, the architecture of Aave v1 is quite different to Aave v2 & v3, making it the most ad-hoc instance of Aave.

On 6th of february a first set of measures was implemented by the DAO to accelerate the offboarding process, followed by a second proposal on 3th of march.

This Phase 3 is the final phase of the off-boarding as suggested on the forum with some slight modifications:

  • the proposal does not inject capital to core. The rational being that:
    • there is enough liquidity for even the biggest account of each asset to withdraw.
    • it's not possible to calculate the exact amount of bad debt as some of the debt is collateralized with a basket of relatively small collateral positions.
    • if a situation in which a user cannot withdraw due to liquidity constrains ever occurs the treasury managers can easily inject capital at any point.
  • the proposal also replaces the stable asset oracles with the capo oracles introduced on aave v2 for consistency across the pools.

Specification

Upon execution the proposal upgrades the following contracts:

  • POOL: in order to disable all actions, but liquidation, repay & withdraw
  • POOL_CORE: in order to update the index upon IR updates
  • POOL_LIQUIDATION_MANAGER: in order to increase the static liquidation penalty from 3% to 5%, while reducing the gas overhead

Also, the proposal will change the pool configuration:

  • all reserves interest rate strategies will be replaced with a zero interest rate strategy
  • the stablecoin oracles are replaced with the capped oracles also used on ethereum v2

References

Copyright

Copyright and related rights waived via CC0.

by BGD Labs