The four teams protecting the $26 billion deposited in Aave are gone. Chaos Labs, BGD Labs, Aave Chan Initiative and Gauntlet —the architects of security at DeFi's largest lending protocol— departed within a 14-month window. What remains is Aave Labs, alone, migrating to the most complex version in its history.

If you have funds in Aave, this affects you directly. Not because the smart contracts have failed, but because the people who oversaw them, who adjusted the risk parameters, who detected vulnerabilities before they became exploits —they are no longer there.

What is happening with Aave's governance in 2026?

The Aave ecosystem is experiencing the deepest institutional crisis in its history. Between February 2024 and April 2026, the four external teams that underpinned the protocol's development, risk management and governance abandoned their positions. This is not a routine change of service providers: it is a total reconfiguration of the operational architecture of the world's largest DeFi lending protocol.

The pattern is unambiguous. Every team that left denounced the same dynamic: progressive centralization of power in Aave Labs, the protocol's founding entity. What began as a federated ecosystem with multiple independent voices —where productive tension between teams produced more conservative risk parameters— has transformed into a model where a single entity controls the technical, budgetary and strategic direction.

The numbers that matter: Aave generated $142M in revenue in 2025 and reached a cumulative lending volume of $1 trillion in February 2026. Contributors did not leave due to a lack of protocol success, but because of the deterioration of their relationship with Aave Labs. The protocol allocates only 3.5% of its revenue to risk management —less than half the banking standard (6–10%).

Who left Aave and why?

The disintegration of the external contributor team has followed a sequence that industry analysts describe as a process of "covert privatization." Each departure removed a layer of independent oversight, and each one strengthened Aave Labs' position as the central authority.

Date Entity Function Leader Primary reason
Feb 2024 Gauntlet Risk management John Morrow Political friction and inconsistency in DAO guidelines
Feb 2026 BGD Labs Protocol development Ernesto Boado Centralization of power; exclusion from V4 design
Mar 2026 ACI Governance and growth Marc Zeller Unfair rules of engagement; lack of budget transparency
Apr 2026 Chaos Labs Risk management Omer Goldberg Divergence over V4; structural economic losses

The loss of BGD Labs is particularly devastating from a technical standpoint. The team was founded by Ernesto Boado, Aave's former CTO. BGD was not just any external provider: it was the custodian of the V3 codebase and the cross-chain security verification infrastructure. Losing BGD means losing the institutional memory of those who built the version that currently safeguards $26B in deposits. It is as if the architect of a skyscraper abandoned the project just before adding 20 more floors.

The departure of Gauntlet in 2024 was the first warning sign. After leaving Aave, it migrated to Morpho Blue —a clear signal that the best risk teams were choosing the competition. But it was an isolated case the community was able to absorb. What followed was a chain collapse.

Why did Chaos Labs leave Aave?

The departure of Chaos Labs on April 6, 2026 is the definitive turning point. For three years, Chaos Labs was the architect of Aave's economic stability, overseeing TVL growth from $5B to over $26B with a material bad debt rate of zero. That is an impeccable track record that few teams in DeFi can match.

But Chaos Labs operated at a loss during those three years. Its annual budget was $5M —the amount the DAO was willing to pay— against a minimum operational cost of $8M. Chaos subsidized Aave's security with its own capital for 36 months, waiting for a budget alignment that never came.

Omer Goldberg, CEO of Chaos Labs, identified three irreconcilable factors:

1. Architectural divergence: The transition to V4 is not an incremental upgrade, but a total reconstruction that doubles the operational load. Chaos had to simultaneously manage V3 and V4 during a migration period that could last years. V4 risk models must be built from scratch: the liquidation logic and credit frameworks are fundamentally different.

2. Economic unsustainability: $5M represents only 3.5% of 2025 revenues of $142M. Traditional banking standards allocate between 6% and 10% of revenue to compliance and risk functions. A protocol aspiring to institutional scale cannot spend less than half of what a conventional bank spends on protecting its users' funds.

3. Existential risk asymmetry: The profit potential for the risk manager is marginal, but the legal and reputational liability in the event of a systemic failure is unlimited. Without clear regulatory frameworks for DeFi, Chaos Labs assumed unlimited risk for a return that did not even cover its operating costs.

Item Value Context
Aave revenue (2025) $142M Total generated by the protocol
Budget offered to Chaos Labs $5M 3.5% of revenue
Actual minimum operating cost $8M 5.6% of revenue
Annual loss for Chaos Labs ~$3M Subsidized with own capital for 3 years
Banking standard for risk 6%–10% Of total revenue

Chaos Labs argued that a protocol with $26B in deposits and $142M in revenue was spending less on security than a fintech startup spends on compliance. The DAO chose to save $3M annually and lost the team with the best risk management track record in all of DeFi.

Why do they accuse Aave Labs of centralizing power?

BGD Labs and ACI pointed directly at Aave Labs for concentrating decision-making. The accusations are not abstract —they are backed by documented on-chain facts and public DAO votes.

The CowSwap scandal (December 2025). It was discovered that Aave Labs had been diverting fees from the CowSwap collaboration into its own corporate treasury instead of depositing them into the DAO treasury. This is not a minor accounting error: when the entity receiving the largest DAO budget also diverts revenues belonging to the DAO, institutional trust breaks down. This event was the direct catalyst that led ACI to conclude that no viable role remained for independent service providers.

The brand assets vote. BGD Labs proposed transferring web domains, social media accounts and intellectual property rights to the DAO —a basic decentralization step that would guarantee the protocol did not depend on a single entity for its online presence. The proposal was rejected with 55% of votes against. Marc Zeller denounced that the vote was influenced by the large AAVE token holdings of entities linked to Aave Labs —that is, Aave Labs used its voting weight to block a transparency measure that would limit its own control.

Undisclosed voting power. Marc Zeller (ACI) articulated the core problem: it makes no sense to have independent service providers when the recipient of the largest DAO budget exercises undisclosed voting power over its own funding proposals and those of its competitors.

The "Aave Will Win" framework: To fill the void left by contributors, Aave Labs proposed a budget of $42.5M and 75,000 AAVE tokens. It passed with only 52.58% of votes —the narrowest majority in DAO history. The framework promises to direct 100% of Aave-branded product revenues to the DAO treasury, but critics see it as a de facto monopoly: Aave Labs funds its development with DAO money, controls the technical direction, and has enough voting power to approve its own proposals and reject others.

What is Aave V4 and why is it risky?

The departure of the risk and development teams occurs precisely when Aave is deploying its most complex upgrade: V4. This version introduces a "hub-and-spoke" architecture that unifies liquidity across all networks, improving capital efficiency but creating a new and dangerous vector: a failure in any spoke can drain global hub liquidity.

The problem is not just the complexity of V4 itself. It is that V3 and V4 will coexist during a migration period that could last years. This means dual market management: risk oracles must process twice the data and anticipate interactions between old and new liquidity. Without the accumulated expertise of Chaos Labs and BGD Labs, the protocol faces an "institutional memory void" that could delay its response to oracle manipulation attacks or liquidity crises.

Attribute Aave V3 (proven) Aave V4 (new) Risk implication
Liquidity structure Isolated markets per chain Unified hub (hub-and-spoke) Failure in one spoke can affect global liquidity
Liquidation logic Individual contracts Unified and modular liquidation Greater complexity in cascade simulations
Oracle dependency Deep integration with Chainlink Proposed proprietary oracles Potential data centralization
Risk oversight Multi-layer federated model Consolidated in Aave Labs/LlamaRisk Less diversity in adversarial models
Oracle operational load Data from one version V3 + V4 data simultaneously Doubled load during coexistence period

Chaos Labs' concern was not only technical but philosophical: V4's infrastructure was not designed with their input. They were being asked to assume responsibility for a system they had no part in designing and which they considered inherently harder to secure than V3.

What happened with the $50 million incident at Aave?

The fragility of the ecosystem during the transition became apparent on March 12, 2026, with a spectacular loss that reverberated across all of Crypto Twitter. A user attempted to swap 50.4 million aEthUSDT for aEthAAVE through the Aave interface. The result: they received $36,000 in assets —a 99.93% loss of value.

What went wrong? The CoW Swap aggregator integrated into the interface selected routing paths with insufficient liquidity for an operation of that magnitude. But the loss did not stop there: an MEV (Maximal Extractable Value) bot executed a sandwich attack that captured an additional $10 million from the transaction's inefficiency. Of the original ~$50M, $36K went to the user, ~$10M to the MEV bot, and the rest evaporated in extreme slippage.

Aave's response: "Aave Shield" was created, a feature that blocks by default any swap with a price impact greater than 25%. Although the incident was not a failure of the lending protocol itself, but of the interface layer and third-party swap services, it underscored exactly what Chaos Labs had been warning: the scope of risk is expanding into user-facing applications and developer tools, areas where legal and operational liability is even more diffuse than in smart contracts.

This event is a brutal reminder that security in DeFi is not limited to smart contracts. Interfaces, aggregators and liquidity routes are attack surfaces requiring constant oversight —precisely the kind of oversight the teams that just left were providing.

Who manages Aave's risk now?

Following Chaos Labs' departure, LlamaRisk has emerged as the successor for protocol risk management. With a team of 16 professionals, LlamaRisk proposes a fundamental paradigm shift: moving from the "delegated management" model —where external firms make decisions with opaque methodologies— to one of "protocol-owned risk infrastructure."

LlamaRisk's main criticism of Chaos Labs' previous approach is that it operated as a "black box": private methodologies, proprietary models, and decisions the DAO had to accept without the ability to audit the underlying reasoning. LlamaRisk proposes building tools on top of the Chainlink (CRE) infrastructure that are fully auditable and controllable by the DAO.

Aspect Chaos Labs (previous) LlamaRisk (current)
Methodology "Black box" with proprietary models Auditable and open-source tools
Infrastructure Private internal systems Built on Chainlink (CRE)
Governance Decisions delegated to the team Controllable by the DAO
Automation Frequent manual interventions LlamaGuard NAV (automatic safeguards)
Team Established team (3 years at Aave) 16 professionals, in integration phase

LlamaRisk's approach —open infrastructure vs. black box— is philosophically attractive. But the transition occurs under extreme pressure. LlamaRisk must absorb Chaos Labs' functions, become familiar with the risk parameters of dozens of markets across multiple chains, and prepare for the dual management of V3+V4, all simultaneously. Building institutional expertise takes years; the protocol needs results in months.

Oracle monitoring, parameterization of new assets and automatic safeguards such as LlamaGuard NAV are the immediate priorities. But the real test will come with the first market crisis under their supervision —an event that tends to arrive without warning.

Can Aave lose its dominant position in DeFi?

Aave remains the giant of DeFi lending, but internal instability is feeding the competition. Protocols such as Morpho and Spark have seized on the governance crisis to attract both talent and capital.

The most revealing example: Gauntlet, after leaving Aave in 2024, migrated to Morpho Blue. When the best risk teams choose your competitor, it is a signal the market does not ignore. If BGD Labs engineers end up building for another protocol, the talent exodus will become a capital exodus.

The previous "two-layer risk" model —where Gauntlet and Chaos Labs frequently held divergent opinions— forced debates that resulted in more conservative and robust parameters. That productive tension was a feature, not a bug. The current consolidation under Aave Labs and a single risk partner (LlamaRisk) could accelerate decisions, but also increase vulnerability to shared errors of judgment or group bias.

The three factors that will determine Aave's future:

1. Technical absorption: Aave Labs must sustain V4 innovation while securing the $26B deposited in V3, without the support of the original BGD Labs engineers or the former CTO who founded the team.

2. LlamaRisk's efficiency: 16 professionals must replicate the work that Chaos Labs refined over 3 years, validating their open infrastructure approach quickly enough to recover the confidence of institutional investors who view Chaos Labs' departure as a "bad omen."

3. Governance legitimacy: The DAO must find balance between Aave Labs' leadership and the transparency demanded by the community. With the CowSwap scandal and the brand assets vote as precedents, the credibility of the governance process is at an all-time low.

What does this mean for Aave users?

For users with funds deposited in Aave, the situation calls for active vigilance but not panic. V3's smart contracts continue to function as designed. However, there are practical considerations that can protect your capital:

Monitor the V4 migration. The coexistence of V3 and V4 introduces complexities that even the teams that left considered difficult to manage. Before migrating funds to V4, wait for LlamaRisk to publish its first independent risk assessments of the new architecture. Early adopters bear disproportionate risk at this stage.

Diversify across protocols. Concentrating all deposits in a single protocol during a governance transition period increases risk. Evaluate alternatives such as Morpho, Compound or Spark as complements —not replacements, but layers of diversification.

Use verified interfaces. The $50M incident demonstrated that interfaces can be vectors of massive loss. Use Aave's official interface, enable Aave Shield to limit price impact on swaps, and never execute large-scale operations without verifying available liquidity on the route.

Watch parameter adjustments. With a new risk team in charge, changes to collateralization factors, liquidation thresholds and lending limits deserve special attention. A calibration error in V4 could trigger cascade liquidations across hundreds of protocols that depend on Aave as a liquidity layer.

With CleanSky you can monitor your DeFi positions in real time and assess the health of your deposits in Aave and other lending protocols.

Conclusion: The end of an era in DeFi governance

The Aave contributor exodus represents the most significant transformation in the governance of a top-tier DeFi protocol. The shift from a federated multi-specialist model —where tension between independent teams produced better decisions— to a "sovereign company" model under Aave Labs is a high-stakes bet with $26B on the line.

Aave has demonstrated technical resilience for years. The question is no longer whether the technology works, but whether an organization that has lost its most experienced guardians —the former CTO and his development team, the risk manager with a perfect 3-year track record, the ecosystem's most vocal governance leader— can maintain the discipline needed to safeguard assets of this magnitude during the most complex migration in its history.

The next 12 months will determine whether the consolidation of power in Aave Labs was a necessary measure for institutional scale or the beginning of a decline caused by the erosion of its decentralized character. The market will watch every parameter adjustment in V4. In a volatile asset environment, survival itself is the most valuable product —and Aave has just lost the guardians who secured that survival for the past three years.

Related articles: To compare alternatives, read Aave vs Compound vs Morpho: which to choose in 2026? To understand protection mechanisms, see How liquidations work in DeFi. Monitor your Aave positions with CleanSky —view your approvals, liquidation risk and P&L in real time.