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

marsbit2026-04-24 tarihinde yayınlandı2026-04-24 tarihinde güncellendi

Özet

An article titled "Aave Is Giving Up Its Throne in DeFi Lending Due to Its Own Foolishness" discusses how Aave mishandled a crisis following a $292 million hack of rsETH from Kelp DAO, leading to significant outflows and reputational damage. After the hack, Aave failed to promptly reassure users or commit to covering potential bad debt—estimated between $123.7 million and $230.1 million—despite having sufficient reserves. This hesitation triggered panic, resulting in $17.2 billion in outflows and liquidity crises across multiple pools. The author argues that Aave’s poor crisis management and reluctance to act quickly exacerbated the situation, damaging its reputation as the "safest DeFi" platform. Meanwhile, competitor Spark, a fork of Aave V3, capitalized on the situation by attracting fleeing funds, growing its TVL by nearly $2 billion. Spark had previously delisted rsETH, avoiding any exposure to the hack. Its proactive communication and strategic positioning contrast sharply with Aave’s delayed response. Although Aave’s founder later announced a relief plan (DeFi United) with multiple partners and a personal donation, the damage to user trust and liquidity may be lasting. The article concludes that Aave’s missteps have allowed competitors like Spark, Morpho, and Jupiter Lend to challenge its dominant position in DeFi lending.

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 the community's panic sentiment ferment for several consecutive days due to its extremely foolish crisis PR strategy, thereby losing its once greatest advantage in the lending track—hundreds of billions of dollars in deposited funds and the user mindset label of "the safest DeFi".

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

What Did Aave Do Wrong?

The details of the Kelp DAO hack need not be repeated; blaming Aave for why it granted rsETH such a high LTV is meaningless now. 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 might be two possible bad debt scenarios—if the stolen loss is written off from all rsETH in circulation, it is expected to generate $123.7 million in bad debt; if the value of mainnet rsETH is protected and the loss is fully recorded 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 capability to cover it with its reserves from Umbrella, the DAO treasury, and the team. I understand that Aave is unwilling to pay this money itself and wants the main responsible party, Kelp DAO, and the secondary responsible party, LayerZero, to contribute as much as possible. But the problem is that the other parties will think the same way—"Aave is so rich, the situation is so awkward, it should bear more." Therefore, in the short term, it is difficult for these three parties to reach a consensus, which implies that 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 with Aave are all attracted by its reputation, security, and liquidity. However, the situation now is that in the most critical days after the incident, Aave consistently failed to give users some kind of bottom-line guarantee promise, but instead kept emphasizing "our code has no problems" and "how rsETH is accounted for is beyond Aave's control" to shift blame.

This is why panic sentiment kept fermenting within the community. Users tried every means to escape and avoid risk: those who could withdraw directly did so, and those who couldn't went to borrow from other pools first, causing the impact to gradually expand. So Aave's current situation is: on one hand, it faces continuous fund outflows; 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 didn't it inject a dose of reassurance into the community from the beginning 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;后续 could continue to dispute with LayerZero and Kelp DAO.

Now, it's done. For the sake of a promised relief of at most $230 million, Aave watched $17.2 billion in deposited funds flow out (the number may continue to grow), and this doesn't even include the decline in AAVE's price these days... No matter how you calculate it, it's a huge loss.

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.

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

Behind Aave, Spark Is Watching Covetously

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

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涉嫌 breaching the contract, and coupled with route differences, the two are now purely competitive.

Three months before the Kelp DAO theft, Spark had just removed support for rsETH (for details, please refer to "Same Day, Different Fate: Aave Embraces rsETH and Loses Nearly $200 Million, Spark Exits Unscathed"). You call it strategic conservatism or rigorous risk control, or even attribute it entirely to luck, but the result is that Spark was not affected at all in this incident—on this point alone, Spark can wantonly attack Aave's former "safest DeFi" label.

Thus, 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 continued accumulation in recent days, the total deposit has reached $1.3 billion—in the DeFi world, Brother Sun's operations are really something to learn.

On April 23, Upbit officially announced the launch of the Spark (SPK) Korean Won trading market. SPK, stimulated by this positive news, rose over 80% in a single day, significantly narrowing the market value gap between itself and 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 that 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 frequent KOL speaking out on this matter, posting dozens of times a day. Although his发言 can indeed help the public understand what happened, it objectively also加剧 the panic sentiment surrounding Aave.

But this is the purest商业 competition; MonetSupply just made the most correct choice.

Aave Is Losing the Throne of DeFi Lending

In the early morning of April 24, perhaps realizing the严峻 situation, Aave founder Stani announced on X the launch of a relief plan called DeFi United. Cooperative participants include LayerZero, Ethena, ether.fi, Ink Foundation, Golem Foundation, Trydo, etc. Stani personally will also donate 5,000 ETH to solve the current problem.

But the funds have already flowed out, and user trust has been severely damaged. Relying solely on this belated statement, Aave will find it difficult to regain deposited funds and user trust in the short term.

The DeFi lending track has long presented a pattern of "one superpower, multiple great powers," with Aave一直以来 having seemingly extremely solid leading advantages. But now, Aave is拱手 surrendering the throne. Behind it, challengers are coming aggressively; 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 luxury house in London for approximately $30 million, one of the most expensive transactions in the UK's sluggish luxury real estate market in the past year. I don't know if there is something like a "jinx," but with precedents like Su Zhu and others, it seems that big shots who consume conspicuously within the circle always run into some倒霉事.

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

İlgili Sorular

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

AAave's extremely poor crisis management strategy, which failed to provide a timely and reassuring commitment to cover the potential bad debt, led to widespread community panic and a user rush to withdraw funds.

QWhat are the two potential bad debt scenarios calculated by Aave after the rsETH exploit?

AIf the stolen loss is written off from all rsETH in circulation, it would result in approximately $123.7 million in bad debt. If the value of mainnet rsETH is protected and the loss is fully attributed to the mapped version of rsETH on Layer 2, it would result in approximately $230.1 million in bad debt.

QWhich competitor protocol directly benefited from the funds flowing out of Aave, and what was a significant factor in its immunity to the hack?

ASpark Protocol directly benefited, with its TVL growing by nearly $2 billion. A significant factor was that Spark had removed support for rsETH three months prior to the hack, avoiding any exposure to the incident.

QWhat was the name of the key initiative announced by Aave founder Stani Kulechov in a belated attempt to address the crisis?

AStani Kulechov announced an initiative called 'DeFi United,' a relief plan involving partners like LayerZero and Ethena, to which he also personally pledged a donation of 5,000 ETH.

QAccording to the author, what is the fundamental reason users traditionally deposited funds into Aave, given its uncompetitive yield rates?

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

İlgili Okumalar

It Took Me a Year to See the Hard Truth About Agent Payments

**Title: It Took Me a Year to See the Hard Truth About Agent Payments** Over the past year, I've worked on infrastructure for the Agent economy, engaging with major players like Stripe, Visa, Coinbase, and numerous startups. The findings reveal a stark reality: genuine, widespread demand for Agent-based payments does not yet exist. **Key Observations:** * **Agent-to-Merchant (Shopping):** The user experience for AI shopping often falls short, especially for visual product discovery. While AI excels at understanding needs, conversational interfaces can't yet replace browsing and comparing multiple products visually. Current merchant interest is largely defensive ("Agent Engine Optimization") for a future that hasn't arrived. High-frequency, low-friction purchases (like food delivery) are potential fits, but lack open APIs and face high AI inference costs. Simpler, more affordable, or cross-language interactions for complex UIs are a niche opportunity but require massive consumer distribution to scale. * **Agent-to-API (Developer Tools):** Developer payment needs for APIs (computing, data, models) are already met through subscriptions and prepaid credits. The core challenge is not payment friction but supplier economics: most large SaaS providers prefer enterprise contracts over micropayments for API calls. Protocols like MPP and x402 suit the long-tail of smaller services but cater to a developer market historically reluctant to pay for these tools. Major infrastructure needs at the top of the stack are already being addressed. * **Agent-to-Agent (Machine Commerce):** This is a long-term vision with almost no current transaction volume. While a future with high-speed, high-frequency, multi-party machine-to-machine transactions would require novel infrastructure, it remains theoretical. The market is not here yet. * **Agent-to-Finance:** This is the only category with clear, present demand. Financial professionals and DeFi users already pay for tools, and AI augmentation is a natural evolution. Autonomous AI agents can enable entirely new financial strategies. However, competition is fierce from established, regulated incumbents who can more easily layer AI onto their existing products. **The Core Insight:** Companies, especially giants with long time horizons, are building defensively for a potential future of mass machine commerce. For them, early investment is a low-cost hedge. For startups, the current market reality is different. The primary challenge isn't just moving money between agents (payments). The larger, unsolved problem is **orchestration** – coordinating work between agents and humans, verifying outcomes, and then settling. Payment is just a part of settlement, which is just a part of orchestration. Companies that solve the orchestration problem will subsume payments, not the other way around. After a year of building, we see the real, growing, and underserved market opportunity lies in this broader domain of orchestration.

链捕手17 dk önce

It Took Me a Year to See the Hard Truth About Agent Payments

链捕手17 dk önce

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

A researcher discovered a critical "infinite mint" vulnerability in the Zcash cryptocurrency's Orchard protocol using Claude Opus 4.8, leading to a swift fix but also a 50% market drop, erasing billions in value. This incident highlights a new era where powerful, accessible AI models are dramatically lowering the barrier to finding software vulnerabilities. Previously, the security community feared specialized models like Claude Mythos Preview, capable of finding decades-old zero-day exploits. The Zcash case, however, involved a publicly available, general-purpose model. This shift makes advanced security auditing—and attack capabilities—accessible to far more people, not just experts. The mass democratization of vulnerability discovery brings a dual challenge: a flood of low-quality, AI-generated false reports that overwhelm maintainers, and the real, rapid uncovering of deep, dangerous bugs. Open-source projects, often understaffed and unfunded, are particularly vulnerable to this "attention DDoS." The article cites examples like curl shutting down its bug bounty program due to the unsustainable workload. Our perceived digital safety has often been luck, relying on the high cost and effort required to find deeply hidden flaws in complex systems, as seen with historical vulnerabilities like Heartbleed or Baron Samedit. AI changes this cost structure, effectively "mass-producing flashlights" to illuminate every corner of our codebase. While large companies operate extensive security chains involving external white-hat hackers and massive defensive operations, the global cybersecurity workforce faces a severe shortage, especially of experienced personnel capable of analyzing complex threats and coordinating fixes. The core dilemma emerges: AI makes *finding* bugs cheap and scalable, but *fixing* them remains a slow, expensive, and human-intensive process. The article concludes that AI won't destroy the internet but acts as a bright light, revealing that our digital existence is not inherently secure but is precariously maintained by ongoing human effort. The true cost in the AI era may not be discovery, but whether there will be enough people left willing and able to do the hard work of repair.

marsbit50 dk önce

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

marsbit50 dk önce

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

"Codex Goal Mode: How to Make AI Work Continuously Toward a Specific Goal" OpenAI's Codex "goal mode" (/goal) transforms the AI from a reactive code assistant into a proactive execution agent capable of working autonomously for hours or even days to achieve a defined objective. To maximize its effectiveness, follow these key principles: 1. **Define Clear, Verifiable Exit Criteria:** The goal prompt should be a concise, measurable success condition, not a lengthy specification. Use quantifiable metrics like "reduce build time by 30%" or "achieve 100% test parity." 2. **Provide Initial Guidance and Tools:** Direct Codex toward likely problem areas and specify available tools (e.g., browsers, testing environments) to prevent it from exploring unproductive paths. 3. **Enable Progress Measurement:** Equip Codex with ways to track advancement, such as creating comparison tools for visual tasks or evaluation sets, ensuring it can gauge its own progress. 4. **Use a Realistic Execution Environment:** For tasks like performance optimization, provide access to environments that closely mimic production (e.g., similar configs, databases) to yield valid results. 5. **Be Cautious with Visual Goals:** Avoid vague "pixel-perfect" instructions. Instead, supplement visual references with functional checklists or design system specifications to prevent Codex from obsessing over minor details. 6. **Implement Progress Tracking:** For long-running tasks, have Codex commit code to draft PRs, update progress documents, or send Slack updates to maintain visibility into its work. 7. **Review and Consolidate Results:** Once the goal is met, instruct Codex to review its work, clean up ineffective experimental code, and reflect on what strategies succeeded or failed. Ultimately, using goal mode shifts the developer's role from writing prompts to managing a persistent engineering agent—defining objectives, establishing metrics, configuring environments, and conducting final reviews.

marsbit2 saat önce

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

marsbit2 saat önce

From Ethereum to AI's 'CROPS': What Exactly Is This 'Slow Variable' That Vitalik Has Repeatedly Emphasized?

Recently, Vitalik Buterin has frequently emphasized the concept of "CROPS," first outlined in the Ethereum Foundation's March mandate as core principles guiding its focus: Censorship Resistance, Capture Resistance, Open Source, Privacy, and Security. CROPS represents Ethereum's commitment to providing foundational capabilities for user sovereignty—enabling asset ownership, identity expression, and coordination without reliance on centralized platforms or surrendering ultimate control. This framework is gaining new urgency with the rise of AI, particularly AI agents managing digital assets and automating transactions. While AI offers convenience, it risks centralizing user data, intent, and control if dependent on opaque, centralized services. Vitalik argues for "CROPS AI"—AI that is open, privacy-preserving, secure, and capable of local execution to maintain user agency. He highlights convergence between "CROPS Ethereum access layers" and "CROPS AI," such as using zero-knowledge proofs for private remote LLM calls and Ethereum RPC reads, ensuring users can access services without exposing sensitive information. Ultimately, CROPS is not just an abstract ideal but a practical guide for Ethereum's development and AI integration. It addresses the critical long-term question: as digital systems grow more powerful, how can users retain control over their privacy, assets, and autonomy? In an AI-driven era, these principles may define Ethereum's enduring value—prioritizing verifiable, secure, and user-centric design over short-term optimizations like speed and cost alone.

marsbit2 saat önce

From Ethereum to AI's 'CROPS': What Exactly Is This 'Slow Variable' That Vitalik Has Repeatedly Emphasized?

marsbit2 saat önce

İşlemler

Spot
Futures

Popüler Makaleler

AAVE Nasıl Satın Alınır

HTX.com’a hoş geldiniz! Aave Protocol (AAVE) satın alma işlemlerini basit ve kullanışlı bir hâle getirdik. Adım adım açıkladığımız rehberimizi takip ederek kripto yolculuğunuza başlayın. 1. Adım: HTX Hesabınızı OluşturunHTX'te ücretsiz bir hesap açmak için e-posta adresinizi veya telefon numaranızı kullanın. Sorunsuzca kaydolun ve tüm özelliklerin kilidini açın. Hesabımı Aç2. Adım: Kripto Satın Al Bölümüne Gidin ve Ödeme Yönteminizi SeçinKredi/Banka Kartı: Visa veya Mastercard'ınızı kullanarak anında Aave Protocol (AAVE) satın alın.Bakiye: Sorunsuz bir şekilde işlem yapmak için HTX hesap bakiyenizdeki fonları kullanın.Üçüncü Taraflar: Kullanımı kolaylaştırmak için Google Pay ve Apple Pay gibi popüler ödeme yöntemlerini ekledik.P2P: HTX'teki diğer kullanıcılarla doğrudan işlem yapın.Borsa Dışı (OTC): Yatırımcılar için kişiye özel hizmetler ve rekabetçi döviz kurları sunuyoruz.3. Adım: Aave Protocol (AAVE) Varlıklarınızı SaklayınAave Protocol (AAVE) satın aldıktan sonra HTX hesabınızda saklayın. Alternatif olarak, blok zinciri transferi yoluyla başka bir yere gönderebilir veya diğer kripto para birimlerini takas etmek için kullanabilirsiniz.4. Adım: Aave Protocol (AAVE) Varlıklarınızla İşlem YapınHTX'in spot piyasasında Aave Protocol (AAVE) ile kolayca işlemler yapın.Hesabınıza erişin, işlem çiftinizi seçin, işlemlerinizi gerçekleştirin ve gerçek zamanlı olarak izleyin. Hem yeni başlayanlar hem de deneyimli yatırımcılar için kullanıcı dostu bir deneyim sunuyoruz.

392 Toplam GörüntülenmeYayınlanma 2024.12.11Güncellenme 2026.06.02

AAVE Nasıl Satın Alınır

Tartışmalar

HTX Topluluğuna hoş geldiniz. Burada, en son platform gelişmeleri hakkında bilgi sahibi olabilir ve profesyonel piyasa görüşlerine erişebilirsiniz. Kullanıcıların AAVE (AAVE) fiyatı hakkındaki görüşleri aşağıda sunulmaktadır.

活动图片