@Aave has unfrozen all lending markets on its V3 and V4 deployments, days after a security breach at @Binance prompted an emergency freeze across the protocol. The protocol says its smart con
@Aave has unfrozen all lending markets on its V3 and V4 deployments, days after a security breach at @Binance prompted an emergency freeze across the protocol. The protocol says its smart contracts were not affected and that positions stayed fully collateralized throughout.
Aave said that during the freeze only new deposits and borrows were paused, while withdrawals and repayments continued as normal, according to PANews.
Reopening the markets does not restore full functionality. As an ongoing precaution, the loan-to-value ratio (LTV) of USDT, USDC, USDT0, POL, WAVAX, sAVAX, XAUT, PAXG and OP will temporarily remain at 0, meaning they cannot be used as collateral for new borrowing. The Defiant reports that the restrictions apply wherever the assets are listed, with different rules for existing V3 and V4 positions.
An LTV of 0% stops an asset from backing new loans. It reduces the chance that stolen or volatile tokens could be used to draw liquidity from the protocol, and it limits the risk of bad debt if prices move sharply.
According to Aave's own governance forum post, its risk teams joined Aave Labs, TokenLogic and Certora in a joint response group within 10 minutes of the first reports. They chose a market-wide freeze because the exploiter could swap stolen funds into any listed asset, so freezing only the stolen tokens would have left other routes open. The guardian can also reverse a freeze, whereas cutting supply caps would have needed a governance vote and about five days to restore.
In total, 175 reserves were frozen on Aave V3 across 16 networks and 117 on Aave V4 across four networks. Risk provider LlamaRisk reported that a wallet linked to the exploiter deposited 60 million USDT and borrowed 19,762 Wrapped Ether, worth about $44.6 million at the time, as covered by Cointelegraph. The transaction used Aave's standard borrowing functions and did not involve an exploit of its lending contracts.
Onchain analytics firm Bitquery said the hacker's USDT deposit on Aave remained unfrozen, but that Aave's USDT pool was nearly empty on the morning of 30 October, limiting what could be withdrawn to about $3,185 at the time of its measurement. That figure changes as lenders add or remove funds.
The wider Binance incident is still developing. Binance has estimated that roughly $6.3 billion in assets were affected, with around $3 billion frozen with the help of industry partners, according to crypto.news.
Sources
