Aave’s $25 billion lending empire faces a real test as key contributors exit

Aave commands DeFi lending, with DefiLlama showing $24.51 billion in total value locked and $17.526 billion in borrowed funds. The margin against Morpho, its closest rival, is roughly 4.1 times. Spark, the third-largest competitor, sits at $967.52 million in borrowed funds. Aave ended 2025 with 61.5% active loan market share and 52.4% lending TVL share, according to its own accounting. Over less than two months, three of the most visible independent contributor teams tied to Aave's code, governance, and risk management either announced departures or began winding down. BGD Labs said on Feb. 20 it would cease contributing because “the environment no longer aligns,” with off-boarding beginning by Apr. 1. ACI said on Mar. 3 it would not renew and would wind down over four months. Chaos Labs said on Apr. 6 it was ending its engagement on its own terms, having managed risk across Aave V2 and V3 since November 2022. Aave's governance documents describe an operating chain in which ACI handled growth, Chaos Labs handled risk, and BGD handled technical and security verification. LlamaRisk and the Protocol Guardian serve as risk guardians. ACI itself wrote that every major initiative required the full service-provider chain. Three exits in sequence form a pattern that hits the protocol's documented operating model at the same juncture. Why this matters Aave is still the category leader, so this is not a niche governance dispute. If the protocol can absorb these exits without another operational failure, its dominance looks durable. If it cannot, rivals such as Morpho and Spark gain a real opening at the exact moment Aave is expanding its surface area through V4, GHO and new products. Aave's $17.53 billion in borrowed funds dwarfs Morpho's $4.29 billion and Spark's $968 million, according to DefiLlama data. A configuration error made the governance fight real On Mar. 10, a CAPO oracle misconfiguration pushed the effective wstETH exchange rate roughly 2.85% below market . That deviation triggered approximately $10.938 million in wstETH liquidations across 34 accounts, generating about $26.6 million in liquidation volume. Aave's post-mortem confirms no bad debt, but a reimbursement proposal of 512.19 ETH. As a result, the move would cost the DAO 358.56 ETH, putting the event well past the threshold of a governance footnote. Chaos Labs cited the V3-to-V4 transition as a key reason its exit creates a genuine operational burden. Aave has V4 live on the Ethereum mainnet with three liquidity hubs and deliberately conservative caps, while V3 stays active. Chaos argued in its exit that managing a live overlap between a battle-tested version and a new hub-and-spoke architecture requires materially more risk tooling and staffing, estimating a minimum risk budget of $8 million, versus its historical $3 million engagement and Aave's roughly $142 million 2025 revenue base. The oracle event lends that argument specific weight: even a configuration-layer error caused eight-figure harm to users. What Aave Labs is absorbing Aave Labs is moving quickly to absorb the gap. Its “Aave Will Win” ARFC proposes that Labs take on governance tooling , DAO GitHub maintenance, Guardian coordination, CAPO pricing management, bridge adapter maintenance, governance technical reviews, and much of the proposal lifecycle and incentive infrastructure previously tied to BGD and ACI. The Labs' consolidation argument is that the protocol should not depend on any single external shop. V4 underwent approximately 345 cumulative days of security review, involved four audit firms plus independent researchers, and the public contest and published reports surfaced no critical or high findings. Aave also carries over $250 million in Umbrella first-loss coverage. BGD, though departing from its lead contributor role, has proposed a two-month advisory retainer through May 31, keeping it in a narrower security-focused capacity in the near term. LlamaRisk keeps its Aave engagement, and the new risk-agent architecture assigns Risk Guardian responsibilities to LlamaRisk and the Protocol Guardian. The pro-consolidation logic runs like this: a smaller, well-defined set of accountabilities under Labs means faster execution and cleaner lines of responsibility. That argument works best if Labs can execute without a second operational incident during the V3/V4 overlap. Function Previous lead Current / proposed replacement Why it matters Growth / governance coordination ACI Aave Labs absorbing parts Proposal flow, ecosystem coordination Risk management Chaos Labs LlamaRisk / Protocol Guardian / Labs transition Parameter setting, monitoring, incident prevention Technical / security verification BGD Aave Labs + BGD advisory retainer through May 31 Implementation review, security checks CAPO pricing / governance tooling / GitHub / bridge maintenance BGD + ACI linked workflow Aave Labs Operational continuity during V3/V4 overlap Infographic showing Aave’s governance pivot, contribut