Aave contributors and risk managers are reassessing CRV exposure after the recent Vyper zero-day exploit sharply increased volatility across Curve-related markets. The review centers on a large loan position of more than $60 million and on whether current liquidity would be sufficient in a severe selloff.

The discussion on Aave governance points to a mix of actions already deployed and further changes under consideration, with the stated goal of reducing insolvency risk while steering users toward safer configurations on newer versions of the protocol.

Stress on CRV liquidity and collateral settings

The market update says simulations indicate CRV liquidity has improved since the initial exploit, but may still be inadequate if prices were to fall by 80% or more. In that scenario, the forum post warns that liquidations might not fully protect the protocol from insolvencies.

That assessment has kept attention on both the large CRV-linked position and on broader parameters that govern borrowing against the token. The discussion frames the issue not as a single-account problem alone, but as a market structure and liquidity question made more urgent by the exploit-driven volatility.

Measures already taken on Aave V3

One of the main completed steps is AIP-288, which has been deployed on Aave V3 Ethereum and Polygon. According to the governance discussion, that proposal reduced loan-to-value ratios, liquidation thresholds, and debt ceilings tied to CRV exposure on those markets.

The broader push remains focused on migration toward V3, where contributors argue risk controls are stronger and easier to adjust. The post presents that migration as part of the effort to contain risk without forcing an abrupt unwind across all positions at once.

V2 withdrawals and where capital appears to have moved

The update also reviews changes in Ethereum Aave V2 balances since July 30. It cites an aggregate withdrawals difference of about $563.3 million and breaks the outflows into several categories, including funds with unclear destinations, holdings parked in wallets, assets moved into staked products such as Justin Sun's stUSDT account, migrations to Ethereum V3, and transfers linked to venues such as Compound, Binance, and Huobi.

Several addresses were identified as having shifted tens of millions of dollars into Ethereum V3, in some cases through Aave's migration tool. Other balances appear to have stayed in wallets or moved to centralized exchanges, showing that the reduction in V2 exposure has come through a mix of migrations and outright withdrawals rather than a single coordinated path.

Further proposals under discussion

Contributors say the next planned step is to queue and execute AIP-286, which would set CRV loan-to-value to zero on V2. The governance thread also raises the question of whether the community wants to freeze CRV on V2 Ethereum, noting that earlier attempts to freeze the market had their own debate and results.

Two additional changes are being prepared for discussion as separate AIPs: disabling CRV borrows on V3 Ethereum and Polygon, and lowering the CRV liquidation threshold on V2 Ethereum by 6%. The stated purpose is to help the V2 CRV market unwind over time while limiting the chance that falling collateral values could leave bad debt behind.

Reserve factor debate and what comes next

The thread also touches on reserve factor adjustments, but does not treat them as a central fix for the current situation. In the view presented there, changing CRV's reserve factor alone is unlikely to have a major isolated effect, and similar considerations are mentioned for USDT, where historical changes have shown indirect and uncertain influence on user behavior.

Discussion has involved groups including ChaosLabs, Gauntlet and BlockAnalitica, alongside other community participants. The next confirmed steps are governance clarification around the V2 market, execution of AIP-286, and publication of the new proposals on CRV borrowing and liquidation thresholds, as Aave continues weighing how quickly to deprecate riskier setups without disrupting orderly migration.

Source: governance.aave.com