{"id":2347,"date":"2026-03-11T22:30:20","date_gmt":"2026-03-11T21:30:20","guid":{"rendered":"https:\/\/kriptoblog.hu\/?p=2347"},"modified":"2026-07-25T01:11:33","modified_gmt":"2026-07-25T00:11:33","slug":"aave-oracle-hiba-26m-dollar-likvidalva-mi-tortent","status":"publish","type":"post","link":"https:\/\/kriptoblog.hu\/en\/aave-oracle-hiba-26m-dollar-likvidalva-mi-tortent\/","title":{"rendered":"Aave Oracle Failure: $26M Liquidated \u2013 What Happened?"},"content":{"rendered":"<p>\nAave, a leading decentralized finance (DeFi) protocol, recently experienced a significant security incident resulting in the liquidation of approximately $26-$27 million in positions due to a faulty oracle. This event underscores the critical dependence of DeFi protocols on oracles and the potential dangers of configuration errors. This article details everything you need to know about the cause of the failure, its consequences, and the measures taken by Aave.\n<\/p>\n<h2>What Was the Root Cause of the Issue?<\/h2>\n<p>\nThe source of the error lay in the configuration of the Correlated Asset Price Oracle (CAPO). CAPO is an oracle that tracks the price of correlated assets (e.g., staked Ethereum). The system temporarily undervalued the price of staked Ethereum (stETH), which served as a key collateral asset within the Aave protocol. This undervaluation led the system to incorrectly assess users\u2019 collateralization ratios, triggering an automatic wave of liquidations.\n<\/p>\n<p>\nLiquidations occur when a user\u2019s collateralization ratio falls below a critical level. The collateralization ratio is the ratio of the value of the collateral deposited by a user to the value of the borrowed assets. If the collateralization ratio is too low, the system automatically liquidates the user\u2019s position to minimize losses for the protocol. Due to the inaccurate oracle, user collateralization ratios dropped suddenly and incorrectly, leading to the liquidations.\n<\/p>\n<h2>Which Assets Were Affected?<\/h2>\n<p>\nThe most affected asset was stETH, the staked Ethereum token offered by Lido Finance. stETH represents Ethereum deposited by users into the Ethereum blockchain and includes rewards earned from staking. The error temporarily undervalued the price of stETH, leading to the liquidation of users who used stETH as collateral. The liquidations didn\u2019t only affect stETH, but also other collateral assets, as users often utilize multiple assets as collateral.\n<\/p>\n<h2>How Did Aave Respond?<\/h2>\n<p>\nThe Aave team responded swiftly to the incident. The first step was to disable the faulty oracle to prevent further liquidations. They then began investigating the root cause of the error and developing a solution. Aave announced that they were working on compensating users for the price errors. The method and timeline for compensation are still being finalized, but Aave is committed to minimizing the damage to users.\n<\/p>\n<h2>What Lessons Can Be Learned for the Future?<\/h2>\n<p>\nThe current incident highlights the critical dependence of DeFi protocols on oracles. Oracles play a key role in the DeFi ecosystem, as protocols use real market prices to determine collateralization ratios, interest rates, and other important parameters. If an oracle is faulty or manipulated, it can have serious consequences for users and the protocol.\n<\/p>\n<p>\nIn the future, DeFi protocols need to place greater emphasis on the security and reliability of oracles. This may include using multiple oracles, sophisticated validation mechanisms, and regular audits. It\u2019s also important for users to be aware of the risks associated with oracles and how DeFi protocols function. Continuous development of blockchain technology and stricter security measures are essential for the long-term sustainability of the DeFi ecosystem.\n<\/p>\n<h2>DeFi and Institutional Capital<\/h2>\n<p>\nWhile security incidents can raise concerns, the DeFi ecosystem continues to attract institutional capital. DeFi protocols offer new opportunities for investors, such as yield farming and liquidity mining. Compared to traditional financial systems, DeFi protocols provide greater transparency, efficiency, and accessibility. An article in Coindesk points out that DeFi is working to rebuild the fixed-income stack for institutional capital, which could lead to significant growth in the long term.\n<\/p>\n<h2>Conclusion<\/h2>\n<p>\nThe recent Aave incident is a serious warning for the DeFi ecosystem. The faulty oracle caused $26 million in liquidations and highlighted the protocols\u2019 dependence on oracles. The Aave team responded quickly to the incident and is working to compensate users. In the future, DeFi protocols need to place greater emphasis on the security and reliability of oracles to minimize the risk of similar incidents. The DeFi ecosystem continues to attract institutional capital, and technological advancements promise significant growth in the long term.\n<\/p>\n<h2>Sources<\/h2>\n<ul>\n<li>  <a href=\"https:\/\/news.bitcoin.com\/what-happened-in-the-aave-oracle-incident-26m-liquidations-explained\/\" target=\"_blank\" rel=\"noopener\">What Happened in the Aave Oracle Incident? $26M Liquidations Explained \u2013 Defi Bitcoin News<\/a> \u2013 2024. m\u00e1rcius 22.<\/li>\n<li>  <a href=\"https:\/\/www.coindesk.com\/opinion\/2026\/03\/21\/how-defi-is-quietly-rebuilding-the-fixed-income-stack-for-institutional-capital\" target=\"_blank\" rel=\"noopener\">How DeFi is quietly rebuilding the fixed-income stack for institutional capital<\/a> \u2013 2026. m\u00e1rcius 21.<\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>Az Aave, a vezet\u0151 decentraliz\u00e1lt p\u00e9nz\u00fcgyi (DeFi) protokoll nemr\u00e9giben s\u00falyos biztons\u00e1gi incidensnek volt kit\u00e9ve, mely sor\u00e1n k\u00f6r\u00fclbel\u00fcl 26-27 milli\u00f3 doll\u00e1r \u00e9rt\u00e9k\u0171 poz\u00edci\u00f3t likvid\u00e1lt a rendszer egy hib\u00e1s \u00e1rforr\u00e1s (oracle) miatt. Az eset r\u00e1vil\u00e1g\u00edt a DeFi protokollok \u00e1rforr\u00e1sokra val\u00f3 kritikus f\u00fcgg\u0151s\u00e9g\u00e9re \u00e9s a konfigur\u00e1ci\u00f3s hib\u00e1k potenci\u00e1lis vesz\u00e9lyeire. Ebben a cikkben r\u00e9szletesen elemz\u00fcnk mindent, amit a hiba [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":5205,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[95],"tags":[],"class_list":["post-2347","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-defi"],"_links":{"self":[{"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/posts\/2347","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/comments?post=2347"}],"version-history":[{"count":1,"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/posts\/2347\/revisions"}],"predecessor-version":[{"id":2644,"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/posts\/2347\/revisions\/2644"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/media\/5205"}],"wp:attachment":[{"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/media?parent=2347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/categories?post=2347"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kriptoblog.hu\/en\/wp-json\/wp\/v2\/tags?post=2347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}