Freezing an asset on Aave halts new supply and borrowing and sets its loan-to-value ratio to zero, but existing positions using that asset are not forcibly closed or liquidated as a direct re
- Freezing an asset on Aave halts new supply and borrowing and sets its loan-to-value ratio to zero, but existing positions using that asset are not forcibly closed or liquidated as a direct result
- A full ban or removal, by contrast, would typically require unwinding or migrating existing positions entirely, a far more disruptive and operationally complex action for a protocol to take
- Because a freeze is reversible through a subsequent governance vote, it functions as a flexible, intermediate risk-management tool rather than a permanent judgment on an asset’s long-term viability
When Aave’s governance process votes to “freeze” an asset, as the protocol’s latest proposal does for nine separate tokens including osETH, LBTC and rETH, it is taking a specific, carefully scoped action that is meaningfully gentler than the alternative of banning or fully removing that asset from the protocol. Understanding the distinction between these two interventions helps explain why protocols like Aave often reach for a freeze rather than a more drastic removal, even when addressing genuine risk concerns.
A freeze specifically halts two things: it stops any new deposits of the frozen asset from being accepted as fresh collateral, and it stops any new borrowing against that asset, typically by setting its loan-to-value ratio to zero. Critically, a freeze does not forcibly close, liquidate, or otherwise disturb positions that already existed before the freeze took effect. Users who already had the frozen asset deposited or borrowed against can generally continue holding or gradually unwinding those existing positions on their own schedule, even though they can no longer add to them.
A full ban or removal, by comparison, is a considerably more disruptive action. Removing an asset entirely from a lending protocol typically requires actively unwinding or migrating every existing position that still involves that asset, a process that can force users into unplanned liquidations or require coordinated migration tooling, depending on how the removal is structured. That operational complexity, and the direct disruption it causes to existing users, is a major reason protocols generally reserve full removal for only the most severe risk scenarios.
Another important distinction is reversibility. Because a freeze is implemented through the same governance mechanisms that could later reverse it, an asset that is frozen today can, in principle, be unfrozen again in the future if the specific risk concerns that motivated the freeze are resolved or if market conditions change. This makes a freeze function as a flexible, intermediate tool for managing emerging risk, rather than a permanent, final judgment that a given asset no longer belongs on the protocol at all.
Understanding this distinction matters for anyone affected by or simply following a protocol’s risk decisions, since a frozen asset, however alarming the headline might sound, typically represents a protocol pausing new exposure to manage a specific risk concern, not an emergency unwind of money already deposited by existing users. The underlying proposal is available on Aave’s governance forum.
This post first appeared in What It Means When Aave “Freezes” an Asset, Versus Banning It Outright