Aave Proposes $3.8B Borrow-Cap Cuts After Binance Incident
Aave risk provider LlamaRisk has proposed lowering borrow caps across 27 Aave V3 reserves and withdrawal limits on six Aave V4 credit lines, removing about $3.8 billion in unused capacity. The proposed limits would sit at roughly 1.02 times borrowing levels before the October 29 Binance hot-wallet incident. Aave had frozen the affected V3 and V4 reserves after the incident. In Aave V3 Core, the WETH cap would fall from 2.4 million to 1.79 million tokens, while USDT and USDC caps would be set at $2.56 billion and $2.27 billion. LlamaRisk says the attacker still holds substantial ETH, stablecoins and governance tokens, and could build large positions quickly when markets reopen. The Aave borrow-cap changes are proposed as a risk-control step through the Risk Steward process, ahead of a gradual reserve unfreezing; they do not indicate that the capped amounts have been borrowed or lost. GHO is excluded. If adopted, the cuts would reduce borrowing headroom for users but are intended to limit exposure as markets reopen.
Neutral
The proposal primarily affects Aave borrowing capacity and risk controls, rather than directly changing the supply or utility of AAVE. In the short term, reduced borrowing headroom and the continued freeze may weigh on activity and could prompt cautious sentiment among Aave users and traders. However, the changes are not evidence of funds lost or new borrowing, and the limits are designed to reduce the chance of rapid, concentrated positions when reserves reopen. That may support confidence in Aave’s risk management and help limit market disruption over the longer term. On balance, the direct price signal for AAVE is mixed and indirect, so a neutral classification is appropriate; actual price action will also depend on the incident’s resolution, the pace of reserve unfreezing, broader crypto-market conditions and any resulting changes in protocol usage.