Aave governance just hit a higher gear, the Aave Chan Initiative (ACI) published a sharply critical audit of Aave Labs, and Aave Labs answered the same day with a Contributions Report defending its value and its billing history. At stake is a proposed $51 million funding package for Aave Labs—and, more fundamentally, who controls the protocol’s development agenda, how spending is justified, and what “accountability” should look like in a DAO that relies on semi-centralized builders.
The clash is no longer a quiet budgeting debate. It has turned into a credibility contest over past work, transparency standards, and governance influence—right as the DAO needs continuity heading into V4 planning. With a key engineering contributor, BGD Labs, announcing it will stop contributing and exit effective April 1, 2026, the dispute now has a hard operational deadline attached.
Two reports, two incompatible stories
ACI, led by Marc Zeller, argues the DAO should treat the $51 million ask as part of a longer pattern of questionable capital efficiency and blurred accountability. ACI’s review alleges roughly $86 million in lifetime capitalization and misused capital connected to Aave Labs’ activity since 2017, and it highlights failed or low-return efforts—pointing to Horizon as a standout example with $5.25 million in costs against $216,000 in recorded revenue.
ACI also lays out how it believes Aave Labs has been capitalized over time, listing $16.2 million from the 2017 ICO, $32.5 million from venture rounds, $31.93 million in direct DAO payments, and about $5.5 million in swap fees it describes as “unapproved.” Beyond the numbers, ACI’s framing is about power: critics cited in the audit describe a pattern of influence concentration over governance and brand channels, using loaded labels like “governance power gaming” and a “slow-motion coup.”
Aave Labs’ response aims to flip the burden of proof: it argues that outsiders are measuring value using the wrong yardstick. In its Contributions Report, Aave Labs says the DAO paid it only $4.625 million since November 2022 and emphasizes work it claims it largely self-funded across engineering, security, legal, and growth—work that is not well-captured by forum activity or visible governance participation.
The lab’s defense is also performance-based: it points to revenue-linked outputs it says it helped deliver and support. Aave Labs cites the WETH borrow loop as generating $37 million in annual revenue—around 28% of DAO revenue—and says the GHO stablecoin has produced more than $22 million in revenue since launch, positioning these as tangible proof that core contributions have paid for themselves.
The practical fallout is already real
Regardless of which narrative wins the vote, the dispute has already changed contributor behavior. BGD Labs—credited in the dispute as a key technical contributor behind the V3 revenue engine—said it will cease contributions and exit effective April 1, 2026, citing misalignment over V4 and “radical changes.”
That matters because DAOs can argue about governance philosophy indefinitely, but protocol roadmaps don’t pause. If BGD’s exit removes a critical slice of post-V3 engineering capacity, the DAO will need to either renegotiate, rapidly onboard replacement teams, or accept development slowdown and higher execution risk.
Founder Stani Kulechov has favored a more token-centric governance model to better align value capture, but that position is now being interpreted through the lens of the broader trust dispute, including allegations around pre-vote token accumulation. In this environment, even legitimate governance design ideas can become harder to land because the community is simultaneously debating motives, incentives, and control.
What the DAO is deciding now
The near-term decision is not just “approve or reject $51 million.” It’s also whether funding comes with tighter reporting, clearer deliverables, and enforceable accountability mechanisms that both sides can live with. With April 1 approaching, the DAO effectively has a shrinking window to stabilize staffing and funding choices so V4 planning doesn’t drift into a capacity gap.