service outage

LlamaRisk Proposes Aave Cap Cuts Before Markets Reopen

0Importance
closedStatus
2News media
3Pieces
Published
Updated
Since then
2 new reports
In
DeFi
Also mentions
ETH

Aave said Threshold Network paused tBTC minting and redemptions on 31 October 2026, and that tBTC is listed on Aave V3 on Ethereum Core, Base, and Arbitrum, with the Base and Arbitrum reserves already frozen. A separate Aave update said the Ethereum Core market still allows repayments, withdrawals, and liquidations, and that it holds about $136.5 million in tBTC deposits.

Key claims & sources

✓
Threshold Network issued a pre-emptive pause of tBTC mints and redeems on 31 October 2026.
✓
Aave said tBTC is listed on Aave V3 on Ethereum Core, Base, and Arbitrum, and that the Base and Arbitrum reserves had already been frozen in earlier asset deprecation rounds.
✓
Aave said repayments, withdrawals, and liquidations continue on its Ethereum Core market after the tBTC reserve freeze.
✓
Aave said its Ethereum Core market holds about $136.5 million in tBTC deposits.

What it means

tBTC is Threshold Network’s bitcoin-backed asset, and Aave V3 is one of the lending venues where it is used across Ethereum Core, Base, and Arbitrum. A pause on minting and redeeming changes how users move between tBTC and the underlying bitcoin exposure, while Aave’s reserve settings determine where the asset can still circulate inside the protocol. The fact that Base and Arbitrum were already frozen before the Ethereum Core market was affected shows this is part of a wider asset-management process inside Aave.

For users who hold tBTC on Aave, the immediate practical point is that repayments, withdrawals, and liquidations remain available on Ethereum Core even after the reserve freeze. That means positions are not fully closed off, but new activity around the asset is constrained. Builders and risk managers using Aave have to track where the asset is still active and where it has already been deactivated.

This case highlights a familiar trade-off in DeFi between keeping a market open and limiting exposure when an external asset process changes. A pause by Threshold Network and a reserve freeze by Aave both show how lending protocols can move quickly to reduce functionality around a token without shutting down the whole market. At the same time, the setup underlines how much user access depends on governance and operational controls rather than on code alone.

What remains open is how long the pause on tBTC minting and redemptions will last and whether Aave will make further changes to the Ethereum Core market. The next update from Threshold Network would clarify when minting and redeeming can resume, and any Aave governance action would show whether the reserve freeze stays limited to the markets already named. Until then, the only confirmed state is that Ethereum Core still supports repayments, withdrawals, and liquidations.

Market reaction i

AaveAAVE the event is about this asset
first headline
-0.4% 2 h before
-0.3% 4 h after
$124.50price at publication
12data points

The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Oct 30 10:21
The Defiant scoop
Breaks the event: $3.7B and $130M
+1 d
Oct 31 10:28
Aave governance forum context
Its angle: communication, transaction, liquidation
+1 d
Oct 31 10:36
The Defiant adds
Sharpens the figure: $136.5M

Other recent incidents

WhenWhat happenedFigure
1 days ago Loopscale Lending · Unknown incident no figure in dollars
1 days ago TENDRIL · Swap Logic Flaw incident $550k
1 days ago $TENDRIL · Smart contract vulnerability incident $555k
3 days ago InsurancePool/CoreVault · Flash loan attack incident $112.3k
4 days ago Solana MEV Bot King · Hot wallet key compromise incident $856k

4280 incidents stored