[ARFC] Temporary Freeze of Long-Tail V2 Assets


A proposal to freeze USDP, GUSD, LUSD, FRAX, sUSD and AAVE on Aave V2.


As part of the deprecation plan for V2 markets, and given the recent market volatility and specifically the USDP price spike, we advise reducing additional exposure to all non-major assets across V2, disabling new supply and borrows.

To minimize the governance overhead, we recommend a temporary freeze vote of all non-major assets across V2, namely USDP, GUSD, LUSD, FRAX, sUSD, and AAVE, via the direct-to-AIP framework.

We plan to submit a follow-up proposal to deprecate these assets through the standard governance process so that the community can decide on the future utilization of these assets.

Furthermore, we would like to highlight the upcoming implementation of CAPO on v2 assets, mitigating the risk of upward Oracle manipulation. This enhancement aims to protect borrowers from unexpected liquidations due to price spikes or potential manipulation incidents, such as the recent surge in USDP prices.


The proposal will call the freezeReserve() function for USDP, GUSD, LUSD, FRAX, sUSD and AAVE.

Next Steps

Following the direct-to-AIP framework, an AIP to implement this proposal will be shared following a 24-hour period.


Chaos Labs has not been compensated by any third party for publishing this ARFC.


Copyright and related rights waived via CC0


What is the plan or criteria for unfreezing? Or should we just treat these assets as effectively no longer usable on Aave?

1 Like

AIP-80 has been published for this proposal.

Thank you in advance for your participation in the vote.

1 Like

The proposal is only for Aave v2 and Chaos has mentioned in the forum post that this proposal will be followed up by a proposal to deprecate these assets via the standard governance process.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.