<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Can Aave recover from this and what happens next?]]></title><description><![CDATA[<p dir="auto"><img src="/forum/assets/uploads/files/1776774195666-4b939a7d-efe2-4887-9b72-2d11c484addb-image.png" alt="4b939a7d-efe2-4887-9b72-2d11c484addb-image.png" class=" img-fluid img-markdown" /><br />
Q: Does Aave have protection mechanisms?<br />
Yes, Aave has a safety system called the Umbrella model, which can help absorb losses. Additionally, Aave holds around $181 million in its treasury that could be used to cover part of the shortfall, depending on how the situation unfolds.<br />
Q: What steps are being taken now?</p>
<p dir="auto">Kelp DAO has paused affected contracts and is working with partners to assess damage and prevent further issues. The final outcome depends on how losses are allocated and whether stolen funds can be recovered. The incident will likely influence future security practices across DeFi, especially for cross-chain bridges.</p>
]]></description><link>https://undeads.com/forum/topic/18811/can-aave-recover-from-this-and-what-happens-next</link><generator>RSS for Node</generator><lastBuildDate>Tue, 09 Jun 2026 08:47:58 GMT</lastBuildDate><atom:link href="https://undeads.com/forum/topic/18811.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 21 Apr 2026 12:23:17 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Can Aave recover from this and what happens next? on Tue, 21 Apr 2026 14:51:57 GMT]]></title><description><![CDATA[<p dir="auto">the exploit involving Kelp DAO and LayerZero highlights how bridge vulnerabilities can escalate into multi protocol crises</p>
]]></description><link>https://undeads.com/forum/post/51368</link><guid isPermaLink="true">https://undeads.com/forum/post/51368</guid><dc:creator><![CDATA[encrypted]]></dc:creator><pubDate>Tue, 21 Apr 2026 14:51:57 GMT</pubDate></item></channel></rss>