Aave avoided collapse, but its $8.45B stress test exposed deeper risks

1. A stress test that showed both strengths and weaknesses

When large sums leave a financial system quickly, hidden weaknesses often become visible. In traditional finance, such situations often lead to emergency lending programs, withdrawal limits or government-backed bailouts.

Decentralized finance (DeFi) works differently.

Aave is one of crypto’s biggest lending platforms. In April 2026, users withdrew about $8.45 billion from the protocol after the KelpDAO rsETH bridge exploit raised concerns across DeFi markets.

Aave’s own smart contracts were not compromised. The pressure came from an external rsETH bridge incident that affected Aave through collateral, borrowing and liquidity channels. The protocol’s core logic continued to function, but the episode was not smooth. Some markets came under severe liquidity pressure, and emergency controls were used to contain the damage.

That made the outcome more complicated. Aave avoided a full breakdown, but the event also showed how quickly stress can spread when assets, collateral and liquidity are closely connected.

For Aave founder Stani Kulechov, the event showed that DeFi had become more mature. But independent analysts reviewing the same data took a more cautious view.

While Aave survived, many questioned whether surviving the event was enough to answer concerns about the real strength of DeFi lending protocols.

2. What led to the $8.45B in withdrawals

The pressure did not begin with a hack on Aave itself. It began with the KelpDAO rsETH bridge exploit in April 2026.

Attackers stole about $292 million worth of rsETH from KelpDAO’s LayerZero bridge. That raised concerns about whether some rsETH tokens were fully backed. The concern quickly spread because rsETH was used across DeFi, including as collateral in Aave markets.

This created a direct problem for Aave. If collateral tied to rsETH lost trust or value, lenders could face bad-debt risk. Users began withdrawing funds as they tried to reduce their exposure before conditions became worse.

The withdrawals then added pressure to Aave’s liquidity. As more users pulled funds, some markets became highly utilized. In simple terms, most of the available liquidity had already been borrowed or withdrawn, making it harder for some users to exit immediately.

The incident showed how an external asset problem can still affect a lending protocol. In DeFi, assets often move across bridges, lending markets and other protocols. A problem in one part of the system can quickly affect another.

That is what made the episode look like a DeFi bank run. Users were not waiting for branches to open or banks to approve transfers. They could react in real time. But the event also showed an important limit: users can try to withdraw at any time, but actual withdrawals still depend on available liquidity and protocol conditions.

Did you know? The largest bank runs in history often unfolded over days or weeks. In DeFi, similar events can happen within hours because blockchain protocols never close, and users can move funds instantly from anywhere in the world.

3. Stani Kulechov’s view: The system held firm

Kulechov framed the incident as evidence of Aave’s resilience. In his view, the core protocol worked as designed, even during a period of heavy stress.

That distinction matters. Aave did not suffer a protocol exploit, but the markets around it still came under pressure. 

As withdrawals increased, some markets reached full utilization. That meant liquidity became limited in those markets, making it harder for some users to withdraw immediately. Aave’s risk managers also had to use built-in controls, including emergency freezes and changes to risk parameters, to contain the damage.

Seen this way, Aave did pass an important real-world stress test, but not without strain. Supporters of the platform point to several features that set DeFi apart from traditional finance.

• Collateral is visible on-chain.
• Risk settings are publicly available.
• Liquidations follow smart contract rules.
• Anyone can inspect protocol activity in real time.

These features can reduce some of the information gaps that have contributed to banking crises in the past. But they do not remove every risk. DeFi lending protocols can still face problems from external assets, bridges, liquidity shortages and fast-moving user behavior.

To supporters, Aave’s survival showed that open, rule-based systems can keep operating under heavy pressure. To critics, the incident showed that transparency alone is not enough. DeFi can still require emergency action when liquidity stress spreads across connected markets.

4. Survival does not mean safety

Critics warn against treating the outcome as full proof that Aave’s design is safe. The protocol survived, but that does not mean every part of the system worked perfectly.

Stress events can be read in different ways. Strong design may explain part of Aave’s performance, but favorable market conditions may have also helped.

External analysts noted that large exposure remains concentrated across many DeFi platforms. When a small group of users controls very large positions, their actions can affect the stability of the whole protocol.

Concentration risk has long been a concern in traditional finance. The same concern applies to DeFi.

If several major borrowers close their positions at the same time during market stress, the impact could be bigger than current risk models expect.

Avoiding a crisis this time does not guarantee the same result next time.

Did you know? Aave first launched in 2017 under the name ETHLend. It later rebranded and grew from a peer-to-peer lending marketplace into one of the largest liquidity pool-based lending protocols in crypto.

5. How Aave manages risk

Aave is more than a basic lending platform. Over time, it has added several layers of protection to help reduce wider risks.

Borrowers on Aave can take loans only within set loan-to-value limits. Liquidation thresholds decide when collateral can be sold. Supply caps limit how much exposure can build around certain assets. Borrow caps limit how much users can borrow.

Isolation Mode helps limit the impact of higher-risk collateral. Efficiency Mode, known as E-Mode, uses special settings for assets that usually move together. Governance, supported by expert risk advisers, adjusts these settings when needed.

During the recent withdrawal surge, these safeguards generally worked as planned. Core protocol functions continued, but some markets came under strain. Utilization reached 100% in major pools, limiting withdrawals for some users.

Still, observers argue that DeFi risk management needs to keep improving. Governance decisions can still take time, and risk models may not adjust quickly enough during fast-moving events.

Stress tests often rely on past events, which may miss new types of spillover risk. The real task is not only to avoid earlier problems. It is also to prepare for threats that have not appeared yet.

6. The hidden risk of connected DeFi platforms

One of DeFi’s biggest strengths is also one of its biggest risks. The same connections that make it useful can also make it fragile.

Composability allows applications to connect and work together. Funds placed in one protocol can support activity in another. This helps new products grow faster and can make the system more efficient. But it also creates more links between platforms.

A loan on one platform may depend on collateral from another. That collateral may then be tied to leveraged positions across other systems. Over time, this can create a complex financial network.

In normal market conditions, composability opens up possibilities that are difficult to find in traditional finance. But during stressful periods, it can increase the risk of problems spreading from one platform to another.

A platform’s strength cannot be judged in isolation. The condition of the wider DeFi system also matters.

Did you know? Traditional banks carry out regular stress tests under regulatory supervision. In DeFi, stress tests often happen unexpectedly in live markets, with real users, real assets and no chance to rehearse.

7. What users should take away

For depositors and investors, the episode is an important reminder. A protocol’s size and reputation should not be confused with complete safety. Users need to understand the assets supporting the protocols they use.

Governance proposals also deserve close attention because they decide the protections around deposited funds. Diversification still matters, even in DeFi.

For builders, the takeaway is just as clear. They should design for extreme conditions and keep testing their basic assumptions. They also need to recognize that transparency alone does not remove wider risks.

The incident shows that strength is best judged through repeated performance across several tests, not one event. One stress test provides evidence, but it does not provide certainty.

8. Aave passed this test, but questions remain

Aave’s ability to handle roughly $8.45 billion in withdrawals deserves attention. The protocol kept working during one of the largest liquidity shocks DeFi has faced.

The result is important, but it should not be treated as the final word on Aave’s risk profile.

Supporters see it as proof that open and transparent systems can survive panic without bailouts or emergency measures. Critics, however, see it as a sign that hidden weaknesses may still exist beneath the surface.

Both views have some truth.

Aave showed that DeFi can withstand heavy pressure. The bigger challenge is making sure that strength holds when the next crisis arrives in an unexpected way.