Aave restores ether borrowing limits after $230 million exploit: what traders should know

Aave restores ether borrowing limits after $230 million exploit means Aave is moving WETH loan-to-value settings back toward normal after emergency limits tied to the KelpDAO rsETH incident. For crypto investors, the signal is clear enough: Aave governance thinks the worst spillover risk has eased. My take: that is not the same thing as an “all clear.” Liquid restaking collateral just gave traders a very expensive warning.

What changed on Aave

Aave’s WETH borrowing limits were restored across several Aave V3 markets after risk managers moved to unwind emergency settings from the rsETH crisis. Aave governance materials listed Ethereum Core, Ethereum Prime, Arbitrum, Base, Mantle and Linea as affected deployments.

For users, the change is simple. Traders can borrow against wrapped ether again under the pre-incident loan-to-value setup in those six markets. In Aave’s eMode categories, governance discussions pointed to caps such as 93% on Ethereum Core and Arbitrum and 90% on Base after the temporary flag comes off. High settings. Useful settings. Dangerous settings if someone treats them like a free leverage coupon.

This does not mean every rsETH-related setting has gone back to normal. Most guides frame parameter restorations as a clean return to business as usual. That is only half right. The emergency action was meant to contain a collateral shock; the reversal is about WETH, one of the deepest assets in DeFi. Aave can reopen ether borrowing while staying stricter with long-tail collateral, bridged assets, or tokens with harder redemption paths.

How the $230 million exploit reached Aave

The exploit centered on KelpDAO’s rsETH and a LayerZero-related bridge flow, not a direct hack of Aave’s smart contracts. The attacker reportedly obtained about 116,500 rsETH, then used that collateral inside Aave to borrow real assets. Estimates for possible bad debt ranged from about $123.7 million to $230.1 million.

The move was collateral transformation. The attacker did not have to break Aave’s lending code if Aave accepted an asset whose backing had suddenly become questionable. Once unbacked or disputed rsETH entered lending markets, the attacker could borrow WETH, wstETH and stablecoin liquidity against collateral that no longer had the same economic value. Why does this matter? Because the weak point was not the loan function; it was what the market agreed to count as good collateral.

Aave moved quickly. It froze rsETH markets and cut loan-to-value ratios to zero. It also stopped new borrowing against the affected token. That prevented more leverage from building on bad collateral. The final damage depended on how losses were split across chains and holders. In the harsher version, markets such as Arbitrum and Mantle absorbed more of the hit.

This is the ugly side of DeFi risk. I’ll be honest: this is the part traders tend to wave away until it lands in their own account. Oracles, bridges and collateral rules can all look fine until one of them stops behaving. A lending market can look solvent under normal price feeds while the asset behind the feed is being disputed. That matters even more for liquid restaking tokens, where value can depend on staking rewards, withdrawals, bridge design, buyer depth and plain old confidence.

Why restoring ether borrowing limits matters

Restoring WETH limits brings back capital-efficient trades that rely on predictable ETH collateral rules. It can improve liquidity and reduce forced position changes. It also gives borrowers a cleaner way to manage debt instead of using emergency workarounds.

Aave is one of the main venues for ETH liquidity. When WETH borrowing power gets restricted, the effect does not stay inside one market. Leveraged ETH staking positions become harder to maintain. Market makers lose flexibility. Some borrowers move to thinner venues, which is usually the last place you want size to go during stress. Restoring the limits takes off some of that pressure and may help borrowing rates settle across DeFi.

For AAVE investors, the governance signal may matter as much as the parameter change. The protocol paused risk, coordinated with outside parties, and then started reopening once recovery funding and technical fixes advanced. Proposal coverage around the recovery also referenced DeFi United support and a Mantle-approved credit facility of up to 30,000 ETH, worth about $68 million at the time.

Still, this is not a full reset. Counter to the usual advice, “more borrowing activity” is not automatically bullish if it comes with looser collateral discipline. Aave earns more when borrowing is active, but the rsETH episode may push governance toward stricter collateral onboarding, lower LTVs for restaking assets, higher reserve factors, and closer reviews of bridge exposure. That may protect the protocol. It may also cut yields for traders using riskier collateral. Both things can be true.

Trading lessons from the rsETH shock

The main trading lesson is blunt: collateral quality can break faster than liquidation systems can clean it up. A token with lots of integrations can become dangerous if its bridge, backing, or redemption route is compromised.

Traders using Aave should separate blue-chip collateral from yield-enhanced collateral. WETH and wstETH still carry smart contract and liquidity risk, of course. But they are easier to model than newer liquid restaking tokens with cross-chain wrappers. A 90% or 93% LTV looks attractive in a spreadsheet. In a stressed market, a small collateral haircut can erase equity when the same trade is stacked across several positions. We tried this logic backward: assume the haircut first, then ask whether the trade still deserves capital.

After events like this, I would watch a few numbers closely: protocol bad debt and available backstop liquidity. Then I would compare the affected collateral size with circulating supply. Here, the disputed rsETH amount was large enough to matter to both KelpDAO and Aave. A trader watching only the spot ETH price would have missed the real issue. The collateral had stopped behaving like ordinary ETH exposure.

Position sizing deserves the dull attention it rarely gets during bull markets. Is this overkill? Not when a single collateral flag can change the economics of an entire loop. If a strategy borrows WETH against correlated ETH assets, the trader should model what happens if borrowing freezes, collateral factors drop to zero, or exits sit behind governance delays. In DeFi, liquidity risk is not only slippage. Sometimes the protocol simply will not let you do what you need to do.

What investors should monitor next

Investors should watch Aave governance, rsETH recovery updates, and any new collateral rules for liquid restaking tokens. Restoring WETH borrowing limits is a useful operational step. The investment impact depends on how much bad debt remains and who absorbs it.

Watch whether Aave’s Safety Module or Umbrella-style reserves are used. Watch whether outside contributors cover shortfalls. Also watch whether affected markets regain normal deposits. AAVE token traders should track borrowing demand, reserve income, governance votes that change LTVs, liquidation thresholds, and supply caps.

The broader comparison is between MakerDAO-style conservative collateral governance and faster DeFi money markets that list new assets earlier. Yes, this slightly contradicts the relief tone above. Bear with me. Aave’s size gives it deep liquidity, but that same size makes collateral mistakes more expensive. For ETH traders, the restored limits help. For portfolio managers, the incident is a reason to discount yields that depend on complicated bridge and restaking assumptions. That discount is the point.

FAQ

Was Aave directly hacked?

No. The incident was linked to KelpDAO rsETH and bridge-related infrastructure. Aave became exposed because the attacker used affected collateral to borrow assets.

What does restoring ether borrowing limits mean?

It means Aave is moving WETH loan-to-value settings back toward their pre-emergency levels on affected V3 markets, so users can borrow more normally against wrapped ether.

How large was the potential Aave loss?

Aave governance discussions and risk reports cited possible bad debt of about $123.7 million to $230.1 million, depending on recovery and loss allocation.

Should traders use maximum LTV again?

Not by default. High LTV trades can work, but the rsETH event showed how fast governance freezes, collateral haircuts and liquidity shocks can hit.

Is this bullish for AAVE?

It is operationally positive because normal borrowing can resume. The token impact depends on final bad debt, recovery funding, user confidence and future collateral policy.