Governance at War: Aave DAO and Aave Labs Clash Over $10 Million in DeFi Revenue

A quiet stream of protocol income has erupted into a full-blown governance firestorm. Aave’s decentralized community and its core development arm, Aave Labs, are locked in a tense dispute over who should control nearly $10 million in annual swap fee revenue — and what this clash means for the future of decentralized governance.

The Revenue That Slipped Through the DAO’s Fingers

At the heart of the controversy is Aave’s “swap facilitator” fee — a small but meaningful cut taken every time users swap assets through the protocol’s integrated services. While the Aave DAO governs the protocol’s parameters and treasury, these swap fees have been flowing not to the DAO, but to a private entity: Aave Labs.

According to community members tracking treasury flows, this revenue — estimated at over $800,000 per month — has been quietly accumulating outside the DAO’s direct control. What triggered the dispute wasn’t just the numbers, but the realization that no formal governance vote had approved this arrangement.

That’s raised critical questions about accountability, transparency, and how decentralized the Aave protocol truly is.

DAO Members Push Back

Tensions boiled over when DAO contributors — including members of service providers like Llama and Chaos Labs — began calling for the revenue to be redirected to the DAO treasury. Several vocal participants on the Aave governance forum have demanded clarity on whether this fee stream is part of the DAO’s authorized economic model, or a side channel operated by Aave Labs for private benefit.

One core contributor bluntly characterized the situation as “unacceptable,” arguing that the community deserves both oversight and control of all revenue sources associated with protocol usage.

But it’s not just about where the money goes. It’s about who gets to decide.

Aave Labs Defends Its Position

In response, Aave Labs has asserted that the swap facilitator service is distinct from the DAO’s operations — a tool it built and operates to enhance the user experience by aggregating and routing swaps. The firm maintains that, because it developed and maintains this functionality independently, the associated fees belong to them.

Aave Labs also argues that these services reduce slippage and improve trade execution for users, creating real value for the ecosystem even if the DAO doesn’t directly receive the revenue.

That’s done little to cool down community frustration. For many DAO members, the issue is less about the tech and more about the principles of decentralized ownership. If core features of a protocol generate revenue but are controlled by a private company, is the project still governed by its community?

Legal Grey Zones and Decentralization Theater

This dispute exposes a deeper ambiguity at the heart of many DeFi protocols. While DAOs are nominally in charge, critical infrastructure — from frontends to backends to integrations — often remains the domain of centralized development teams or companies with limited transparency.

In Aave’s case, the optics are especially thorny. The DAO funds grants, security audits, and strategic partnerships, yet appears to be sidelined when it comes to a growing revenue stream tied to core user activity.

That’s led some critics to accuse Aave Labs of practicing “decentralization theater” — maintaining the image of a DAO-led protocol while quietly monetizing key services in ways that circumvent collective decision-making.

What This Means for DeFi Governance

The implications go beyond Aave. If DeFi is to evolve into a transparent, trust-minimized financial alternative, governance structures must be built to handle conflicts like this — especially when real money is on the line.

This case could set a precedent. If the DAO succeeds in reclaiming revenue control or negotiating a shared structure, it may empower other decentralized communities to reexamine the economic arrangements underpinning their own ecosystems.

On the other hand, if Aave Labs holds its ground and the DAO fails to assert control, the message will be clear: decentralized in name doesn’t always mean decentralized in function.

Next Steps: Proposals, Forks, or Compromise?

For now, the ball is in the DAO’s court. Several governance forum posts suggest a proposal is being drafted to either:

• Formally request revenue-sharing from Aave Labs
• Propose alternative facilitator infrastructure governed directly by the DAO
• Or even fork the protocol’s swap functionality under community control

A fork is unlikely in the short term, but the pressure is real. The DAO has shown in the past — during the Lens Protocol discussions, for example — that it’s willing to push back when core contributors operate in silos.

Whether the two sides find common ground or continue escalating could reshape how major DeFi protocols think about product monetization, contributor compensation, and on-chain transparency.