Aave Is Surrendering the Throne of DeFi Lending Due to Its Own Stupidity

Odaily星球日报Publicado em 2026-04-24Última atualização em 2026-04-24

Resumo

Aave, a leading DeFi lending protocol, is facing a severe crisis and losing its dominant market position due to its poor handling of a recent security incident. The crisis began when Kelp DAO suffered a hack resulting in a loss of $292 million in rsETH. In the aftermath, approximately $17.2 billion in funds flowed out of Aave as user panic escalated. The article criticizes Aave's crisis management as "extremely foolish." Instead of promptly offering reassurance or committing to cover the potential bad debt—estimated between $123.7 million and $230.1 million, which Aave could have afforded—the protocol initially deflected blame, emphasizing that its code was not at fault. This delay and lack of a clear guarantee led to widespread user anxiety, triggering a bank run-like scenario where users withdrew funds or borrowed aggressively from other pools, causing liquidity shortages. Meanwhile, Aave’s competitor Spark—a fork of Aave’s own code—has benefited significantly. Having removed support for rsETH months earlier, Spark avoided any losses from the incident and has since seen its TVL grow by nearly $2 billion, attracting major deposits such as over $1.24 billion from Justin Sun. Spark has actively capitalized on the situation, publicly criticizing Aave’s security reputation. Although Aave’s founder Stani eventually announced a relief plan named "DeFi United" with several partners and a personal donation, the damage to user trust and capital outflows may be irreversible. The ar...

Original | Odaily Planet Daily (@OdailyChina)

Author | Azuma (@azuma_eth)

$292 million, this is the total amount of rsETH funds stolen from Kelp DAO; $17.2 billion, this is the scale of funds that have flowed out of Aave since the incident.

Aave is watching as its extremely foolish crisis PR strategy allows community panic to ferment for several consecutive days, thereby losing its former biggest advantage in the lending track — hundreds of billions of dollars in deposited funds and the user perception label of "the safest DeFi".

  • Odaily Note: For background, please refer to "DeFi Hacked Again for $292 Million, Is Aave Not Safe Anymore?"; "The Tripartite Game Under the $290 Million Hole: Who Will Pay, Aave, L0, or Kelp?".

What Did Aave Do Wrong?

The details of the Kelp DAO hack incident need not be repeated. There's no point in blaming Aave for giving rsETH such a high LTV anymore. Here, I mainly want to discuss Aave's response strategy after the incident from the perspective of a long-term AAVE user.

First is the bad debt scale issue. Aave itself has done the math. Depending on the different handling of rsETH, there could be two possibilities for bad debt — If the stolen loss is written off from all circulating rsETH, it is expected to generate $123.7 million in bad debt; If the value of mainnet rsETH is protected, and the loss is fully accounted for in the mapped version of rsETH on Layer2, it is expected to generate $230.1 million in bad debt.

In either case, Aave has the financial strength to cover it with its Umbrella, DAO treasury, and team reserves. I understand that Aave is unwilling to pay this money itself and wants Kelp DAO, the main responsible party, and LayerZero, the secondary responsible party, to also contribute more. But the problem is, the other parties think the same way — "Aave is so rich, the situation is so awkward, surely they should bear more." Therefore, in the short term, it's difficult for these three parties to reach a consensus, meaning a solution that satisfies everyone is temporarily impossible.

But users cannot wait that long — Aave's yield levels have never been very competitive in the industry. Users who choose to deposit funds with Aave do so for its reputation, security, and liquidity. However, the current situation is that in the most critical days following the incident, Aave consistently failed to give users some kind of bottom-line guarantee promise, instead repeatedly emphasizing "our code is not the problem" and "Aave cannot control how rsETH is accounted for" to shift blame.

This is why panic continued to ferment within the community. Users tried every means to escape the risk, withdrawing directly if they could, or borrowing from other pools if they couldn't withdraw, causing the impact to gradually expand. So Aave's current situation is, on one hand, facing continuous fund outflows, and on the other hand, multiple pools are experiencing liquidity drying up due to utilization rates being maxed out.

This awkward situation could have been avoided (or at least not been this bad)...... Since Aave can afford the money, why not inject a dose of reassurance into the community from the start to prevent a bank run? At most, it's $230 million in bad debt (possibly less), and this money wouldn't necessarily be paid by Aave alone; they could negotiate with LayerZero and Kelp DAO later.

Now, it's done. For the sake of saving on a promise of relief worth at most $230 million, Aave watched as $17.2 billion in deposited funds flowed out (the number may continue to grow), and this doesn't even include the decline in the AAVE token price these days...... by any calculation, it's a disastrously bad deal.

What makes Aave even more uncomfortable is that the worse its situation becomes, the more relaxed opponents like LayerZero and Kelp DAO will be, because they will judge that Aave will be more motivated to solve the problem as soon as possible, which only puts Aave at a disadvantage in the博弈 (game theory).

Having reached this point, Aave has brought this upon itself.

Behind Aave, Spark Is Watching Closely

While Aave is suffering from headaches, the situation for its competitor Spark is booming and extremely positive. What's even more lamentable is that Spark is a competitor that Aave "personally incubated".

Spark was originally a lending protocol forked and developed by Sky (formerly MakerDAO) based on the open-source code of Aave V3. Both sides actually use the same underlying code logic. In return, there was once a profit-sharing agreement between Spark and Aave, but later Aave accused Spark of allegedly breaching the contract, and due to route differences, the two are now in a purely competitive relationship.

Three months before the Kelp DAO theft, Spark had just removed support for rsETH (for details, see "Different Fates on the Same Day: Aave Embraces rsETH and Loses Nearly $200M, Spark Exits Unscathed"). You can call it strategic conservatism, rigorous risk control, or even attribute it entirely to luck, but the result is that Spark was completely unaffected by this incident — on this point alone, Spark can brazenly attack Aave's former label of "safest DeFi".

Consequently, Spark became one of the safe havens for funds fleeing Aave. Since the incident, Spark's TVL has grown by nearly $2 billion (green part in the chart below). On the day of the incident, Justin Sun withdrew 53,665 ETH (worth $124 million) from Aave and subsequently deposited it into Spark. After further accumulation in recent days, the total deposit has reached $1.3 billion — In the DeFi world, Brother Sun's (Justin Sun) moves are really something to learn.

On April 23rd, Upbit officially announced the launch of the Spark (SPK) Korean Won trading market. SPK, stimulated by this positive news, surged over 80% in a single day, significantly narrowing the market capitalization gap with AAVE.

Even Wang Chun, founder of F2Pool, lamented on X: "In the past year, I received 83.7 million SPK rewards from Spark and sold them on CoWSwap for 663 ETH and $1.4 million. Now I kind of regret it."

Spark clearly realizes this is a perfect opportunity to seize market share from Aave's mouth. Since the incident, Spark's Strategy Lead, MonetSupply, has almost become the most vocal KOL on this matter, posting dozens of times a day. Although his comments do help the public understand what happened to some extent, they also objectively exacerbate the panic surrounding Aave.

But this is the purest form of commercial competition. MonetSupply simply made the most correct choice.

Aave Is Losing the Throne of DeFi Lending

In the early hours of April 24th, perhaps realizing the severity of the current situation, Aave founder Stani announced on X the launch of a relief plan called DeFi United. Participating collaborators include LayerZero, Ethena, ether.fi, Ink Foundation, Golem Foundation, Trydo, etc. Stani personally will also donate 5,000 ETH to help resolve the current issue.

But the funds have already flowed out, and user trust has been severely damaged. Relying solely on this belated statement, it will be difficult for Aave to quickly recover the deposited funds and user trust.

The DeFi lending track has long presented a "one superpower, many strong powers" pattern, with Aave一直以来 (yīzhí yǐlái - all along) having a seemingly extremely solid leading advantage. But now, Aave is surrendering the throne. Behind it, challengers are approaching menacingly. Besides the booming Spark, other opponents like Morpho and Jupiter Lend also hope to take a bite out of Aave's share.

Last year, Stani bought a five-story mansion in London for approximately $30 million, one of the most expensive transactions in the UK's sluggish luxury property market over the past year. I don't know if there's something like a "jinx," but following the examples of Su Zhu and others, it seems like big shots in the circle who consume conspicuously always run into some bad luck.

I can't guess what Stani is thinking right now in his five-story mansion.

Perguntas relacionadas

QWhat was the main reason for the massive outflow of funds from Aave following the Kelp DAO hack?

AAave's poor crisis management strategy, which failed to provide timely reassurance or a bailout guarantee to its users, leading to widespread panic and a bank run.

QWhat are the two potential bad debt scenarios calculated by Aave for the rsETH incident, and what are the amounts?

AIf the stolen loss is written off from all rsETH, the bad debt would be approximately $123.7 million. If the value of mainnet rsETH is protected and the loss is fully accounted for in the Layer2 mapped version of rsETH, the bad debt would be approximately $230.1 million.

QWhich competitor protocol directly benefited from the funds flowing out of Aave, and what was the approximate amount of TVL it gained?

ASpark Protocol directly benefited, gaining nearly $2 billion in Total Value Locked (TVL) following the incident.

QWhat was the name of the relief plan announced by Aave founder Stani Kulechov in response to the crisis, and what was his personal contribution?

AThe relief plan was named 'DeFi United'. Stani Kulechov personally donated 5,000 ETH to help resolve the situation.

QAccording to the article, what was the primary reason users traditionally deposited funds into Aave, given its uncompetitive yield rates?

AUsers primarily deposited funds into Aave due to its reputation for safety, security, and liquidity, not for competitive yield rates.

Leituras Relacionadas

U.S. Government Bans Foreign Nationals from Using Fable 5, Anthropic Issues Rebuttal

U.S. Government Bans Foreign Access to Fable 5, Anthropic Issues Rebuttal On June 12th, the U.S. government ordered AI company Anthropic to immediately suspend all foreign access—including foreign nationals within the U.S. and Anthropic's own foreign employees—to its newly released Fable 5 and Mythos 5 AI models, citing national security concerns. This forced Anthropic to temporarily disable access to both models for all users globally, as it cannot technically differentiate user nationality at scale. The models, released just three days prior, represent Anthropic's highest public capability tier. Fable 5 is the first publicly available model from the advanced "Mythos" family, while Mythos 5 is a less-restricted version for approved cybersecurity and critical infrastructure partners. The government's directive was reportedly triggered by claims from another company that it could "jailbreak" Mythos 5, raising alarm within the Trump administration. Anthropic, in a detailed public statement, strongly challenged this rationale. The company argues the demonstrated "jailbreak" is a narrow, non-generalized technique that merely involves identifying minor, known software vulnerabilities—a capability common to other publicly available models like OpenAI's GPT-5.5 and routinely used by cybersecurity defenders. Anthropic stated it has complied with the order but disagrees with the government's standard, warning that applying it industry-wide would halt all new frontier model deployments. The company criticized the lack of a transparent, fact-based legal process and expressed confidence the situation stems from a misunderstanding. It is working to restore access and will release more technical details within 24 hours. Other Anthropic models remain unaffected.

链捕手Há 17m

U.S. Government Bans Foreign Nationals from Using Fable 5, Anthropic Issues Rebuttal

链捕手Há 17m

The Revelation from the Raydium Theft Incident: New DeFi Vulnerabilities Lurking in Forgotten Old Contracts

**Raydium Exploit Reveals DeFi's Hidden Risk: Forgotten "Zombie" Contracts** A recent attack on Raydium's deprecated V3 AMM pools resulted in a loss of approximately $1.34 million. The hacker exploited pools that were no longer supported by Raydium's current UI or SDK but remained fully functional and accessible on-chain. This incident highlights a critical, often overlooked category of risk in DeFi: inactive or legacy smart contracts that projects fail to properly decommission. Since March 2025, there have been at least 8 publicly reported attacks targeting such abandoned contracts, with total losses around $10.8 million. Including older pools and deprecated features, the count rises to 10 incidents with roughly $22.5 million in losses. These "zombie contracts" represent a lifecycle management failure rather than a code vulnerability, yet they are typically misclassified under general "code bug" categories in security reports, masking the true scale of the problem. The root cause is that projects often merely document a contract as "deprecated" without taking essential technical steps to secure it: withdrawing remaining assets, disabling external call functions, and implementing ongoing monitoring. These forgotten, under-monitored components become prime targets for attackers. To address this, the industry needs to recognize "zombie contracts" as a distinct risk category and establish standardized decommissioning protocols. Essential steps should include: 1) a formal retirement announcement, 2) removal of all front-end integrations, 3) withdrawal of locked assets, 4) disabling key contract functions, 5) ongoing security monitoring, 6) clear user communication, and 7) a post-mortem analysis. The value of a DeFi project lies not only in its current TVL but also in the security of its historical codebase, which has now become a new attack surface.

Foresight NewsHá 2h

The Revelation from the Raydium Theft Incident: New DeFi Vulnerabilities Lurking in Forgotten Old Contracts

Foresight NewsHá 2h

Robots Begin to 'Consume Data': The Hidden Production Chain from Indian Data Factories to Billion-Dollar Humanoid Robots

Robots have started to 'consume data,' driving the formation of a new industrial supply chain focused on producing training data for embodied AI. Unlike large language models, which are trained on vast internet text corpora, embodied AI models face a 'data desert' in the physical world. This has created a massive demand for first-person perspective video data (Ego Data), captured by workers wearing cameras in places like Indian garment factories. Companies like Neocambrian AI are establishing 'data factories' where workers perform standardized tasks (e.g., sorting clothes, kitchen organization) to generate thousands of hours of video. Research, such as NVIDIA's EgoScale, demonstrates that scaling this human demonstration data predictably improves robot performance, particularly for dexterous manipulation. This has validated a training path combining large-scale human data for pre-training with smaller amounts of robot-specific data for fine-tuning. The value of different data types varies significantly, forming a 'data pyramid.' The base consists of low-cost, large-scale internet and Ego Data. Higher layers include more expensive motion-capture data (e.g., from data gloves), simulation/synthetic data, and the most costly and scarce layer: real robot teleoperation data. This demand has spawned a layered ecosystem of data suppliers: low-cost data factories, motion capture and alignment specialists, robot-native teleoperation service providers, simulation data companies, and platforms aiming for data standardization. Robot companies themselves are adopting a 'layered procurement' strategy: outsourcing generic Ego Data while building in-house capabilities for robot-specific adaptation data and the critical deployment/failure data generated in real-world applications. The industry is shifting focus from hardware and basic mobility to the data pipelines required for general-purpose capability. While parallels exist to data labeling companies like Scale AI in the LLM boom, the physical complexity of robot data—involving action success ambiguity and sim-to-real gaps—requires more integrated solutions for data collection, annotation, and a continuous feedback loop. The race is on to build the data engines that will teach robots to operate reliably in the unstructured real world.

marsbitHá 4h

Robots Begin to 'Consume Data': The Hidden Production Chain from Indian Data Factories to Billion-Dollar Humanoid Robots

marsbitHá 4h

Trading

Spot
Futuros

Artigos em Destaque

Como comprar AAVE

Bem-vindo à HTX.com!Tornámos a compra de Aave Protocol (AAVE) simples e conveniente.Segue o nosso guia passo a passo para iniciar a tua jornada no mundo das criptos.Passo 1: cria a tua conta HTXUtiliza o teu e-mail ou número de telefone para te inscreveres numa conta gratuita na HTX.Desfruta de um processo de inscrição sem complicações e desbloqueia todas as funcionalidades.Obter a minha contaPasso 2: vai para Comprar Cripto e escolhe o teu método de pagamentoCartão de crédito/débito: usa o teu visa ou mastercard para comprar Aave Protocol (AAVE) instantaneamente.Saldo: usa os fundos da tua conta HTX para transacionar sem problemas.Terceiros: adicionamos métodos de pagamento populares, como Google Pay e Apple Pay, para aumentar a conveniência.P2P: transaciona diretamente com outros utilizadores na HTX.Mercado de balcão (OTC): oferecemos serviços personalizados e taxas de câmbio competitivas para os traders.Passo 3: armazena teu Aave Protocol (AAVE)Depois de comprar o teu Aave Protocol (AAVE), armazena-o na tua conta HTX.Alternativamente, podes enviá-lo para outro lugar através de transferência blockchain ou usá-lo para transacionar outras criptomoedas.Passo 4: transaciona Aave Protocol (AAVE)Transaciona facilmente Aave Protocol (AAVE) no mercado à vista da HTX.Acede simplesmente à tua conta, seleciona o teu par de trading, executa as tuas transações e monitoriza em tempo real.Oferecemos uma experiência de fácil utilização tanto para principiantes como para traders experientes.

416 Visualizações TotaisPublicado em {updateTime}Atualizado em 2026.06.02

Como comprar AAVE

Discussões

Bem-vindo à Comunidade HTX. Aqui, pode manter-se informado sobre os mais recentes desenvolvimentos da plataforma e obter acesso a análises profissionais de mercado. As opiniões dos utilizadores sobre o preço de AAVE (AAVE) são apresentadas abaixo.

活动图片