Aave's guardian multisigs executed reserve freezes across V3 and V4 deployments late on October 29, according to an October 30 update from LlamaRisk, an Aave risk service provider. LlamaRisk reported that the transactions were signed and executed between 21:42 and 23:04 UTC following the Binance incident.
The reported scope was 175 reserves on Aave V3 across 16 networks and 117 reserves on Aave V4 across four networks. These are separate version-specific counts, with overlapping networks.
Which markets were included
For V3, the update names Ethereum's Core and Prime markets, plus Arbitrum, Avalanche, Base, BNB Chain, Celo, Gnosis, Ink, Linea, Mantle, MegaETH, Monad, Optimism, Plasma, Polygon and X Layer.
The V4 list covers the main Ethereum spokes, Avalanche spokes, Base's tokenized-equities spoke and Arc spokes. Horizon's RWA market was excluded from the action.
What the freeze changes
LlamaRisk said a reserve freeze blocks new supplies and borrowing while leaving repayment, withdrawal and liquidation functions active. The provider explicitly stated that no market had been paused. That describes the restrictions imposed by the freeze setting; it does not promise that a particular withdrawal can execute regardless of available liquidity.
The post describes a response coordinated with Aave Labs, TokenLogic and Certora. LlamaRisk said it worked with Aave Labs' engineering team to prepare and simulate the transactions before proposing them to the guardian multisigs.
It also explained the choice of control: guardians can reverse a freeze, whereas restoring caps after cutting them would require a governance vote and approximately five days.
The account was published at about 01:00 UTC on October 30. It described a staged unfreeze to be coordinated with Aave Labs and other service providers, without announcing a reopening date or providing an individual asset-by-asset reserve list.
Related reporting: Chain Incident: Binance investigates potential security issue as CZ describes apparent hack.