A dispute over swap fees put a larger question before Aave’s community: what does token-holder governance actually control when a separate development team runs the products, brand and user interface?
In commentary published on December 16, 2025, at 13:00:36 UTC+8, Chen Mo (cmDeFi) examined the disagreement between Aave DAO and Aave Labs. At the time of that account, discussions were ongoing and no governance vote had taken place.
The integration that exposed the fault line
According to Chen’s account, Aave Labs replaced ParaSwap with CoW Swap in its front-end integration, after which the resulting fees went to a private address controlled by Labs. Anonymous DAO member EzR3aL raised the issue on the governance forum, accusing Labs of “privatizing” protocol value.
Labs’ position was that this was front-end and product revenue belonging to Labs, rather than revenue from the core protocol. The distinction mattered because, according to the article, revenue from the previous ParaSwap integration had flowed to the DAO.
The disagreement was therefore not simply about introducing a swap service. It concerned a change in who received the revenue—and whether that decision belonged to the product developer or the token-governed organization.
One name, two centers of authority
Chen framed the dispute as a tension between Aave as a protocol, governed by the DAO, and Aave as a product, built and maintained by Labs.
Aave DAO consists of AAVE token holders who exercise governance through voting. In the article’s account, the DAO controls core resources, including smart contracts and the treasury, and votes on proposals affecting protocol development.
Aave Labs is the development team responsible for building, updating and maintaining the protocol and products such as the front end and mobile app. It also handles the brand, marketing and partnerships. That public-facing role means Labs is often treated as synonymous with Aave, even though the two entities have distinct powers.
Their work ordinarily overlaps: Labs develops proposals, including changes associated with versions such as V3 and V4, while the DAO votes on implementation. The fee dispute exposed what happens when their interests no longer appear aligned.
Competing ideas of community ownership
Supporters of Labs argued that the CoW Swap integration was a front-end decision, separate from Aave’s underlying architecture. From that perspective, Labs could choose whether to offer the integration and retain its revenue.
DAO supporters saw the change differently. They argued that value should flow to AAVE holders or remain in the treasury under DAO control. The earlier ParaSwap revenue arrangement strengthened their objection to the new destination for fees.
These are competing claims about entitlement, not an established resolution of who owns every revenue stream associated with Aave. For token holders, the dispute tested whether governance rights extend to the interfaces through which people encounter the protocol. For Labs, it raised the question of how much commercial independence a development team retains.
Voting power is not the same as operational continuity
Chen argued that a DAO’s formal authority does not automatically give it the ability to replace a development team smoothly. A decentralized organization can include independent developers, venture investors and large token holders, whose competing priorities may make proposals slower to negotiate and implement.
The article cited Sushi as an example of the damage that internal disputes and leadership changes can cause, while distinguishing operational disruption from smart-contract continuity: a protocol’s functions may remain stable even when its organization changes substantially.
Labs’ supporters also pointed to its contribution to Aave’s development. Chen quoted Stani recalling that Emilio persuaded him to pursue the Aave protocol design in 2018–2019, when the team was still working on ETHLend, and suggesting that Aave might otherwise never have existed.
That history helps explain the tension, but does not itself settle the allocation of revenue or governance rights.
Accountability, funding and clearer boundaries
The article described increasingly pointed exchanges. Emilio argued that people were maliciously diminishing Labs’ contribution; an ACI team member alleged that Labs had repeatedly tried to take advantage of the DAO and had been exposed doing so. These were participants’ claims, not independently established findings.
Chen also summarized Zeller’s criticism of initiatives including Portals, Credit Delegation Vault and Lens, questioning how directly those efforts had translated into protocol revenue or significant adoption. On V4, the article relayed concerns that the DAO had spent $15 million while its value proposition remained unclear compared with V3’s liquidity moat. The suggestion that V4 might become another means of extracting revenue was a concern raised in the dispute, not a demonstrated conclusion.
Chen’s interpretation was that failed experiments are an unavoidable part of research and development, and that Zeller’s criticism called for stronger accountability, transparency and alignment rather than a denial of Labs’ contributions.
Community suggestions summarized in the article included advance disclosure when product revenue would go to Labs rather than the DAO, an explicit revenue-sharing arrangement, and a transparent information page on Aave’s main site or Labs’ site.
Chen favored a negotiated allocation of interests and remained optimistic about Aave’s long-term prospects. But the central unresolved issue was broader than one integration: the founding team and token holders had different expectations of what their shared project—and its governance—entitled them to control.
Original source: Chen Mo (cmDeFi), PANews, published December 16, 2025, at 13:00:36 UTC+8. This article preserves the dispute’s status at that reporting date.