BTCC / BTCC Square / M1n3rX /
Aave DAO Demands Full Control Over Brand and Domains: The Battle for Decentralization

Aave DAO Demands Full Control Over Brand and Domains: The Battle for Decentralization

Author:
M1n3rX
Published:
2025-12-17 16:39:02
14
1


The Aave DAO is making waves in the DeFi space by pushing for full ownership of its brand assets, including domains and social media accounts. This move comes after Aave Labs allegedly redirected $10M in annual fees away from the DAO treasury. Key contributors like Marc Zeller and Ernesto Boado are leading the charge, arguing that the DAO—not Aave Labs—should control the brand’s monetization. Here’s a deep dive into the conflict, the proposal, and what it means for decentralized governance.

Why Is the Aave DAO Fighting for Brand Control?

The AAVE DAO, a decentralized autonomous organization governing the Aave protocol, is locked in a high-stakes battle over who truly owns the Aave brand. On December 4, 2025, Aave Labs reportedly diverted around $10M in annual fees to its own accounts instead of the DAO treasury. This sparked outrage among token holders, with Marc Zeller, founder of Aave Chan Initiative, accusing Aave Labs of "privatizing revenues" without community consent.

Ernesto Boado, an independent contributor since 2022, has now proposed "AAVE Token Alignment - Phase 1: Ownership," demanding that critical assets—like aave.com, GitHub organizations, and social media handles—be transferred to the DAO. Boado argues that Aave Labs’ ability to monetize the protocol relies entirely on the brand recognition built by the DAO. "Without the DAO’s reputation, these products wouldn’t generate revenue," he wrote.

blockquote icon

What’s in the Proposal?

The proposal outlines a transfer of all brand assets to a neutral legal structure, independent of service providers like Aave Labs or BGD Labs. Key demands include:

  • Full ownership of aave.com and onaave.com domains
  • Control over social media accounts (@aave on X, Discord, Instagram)
  • GitHub organizations ("aave" and "aave-dao")
  • The npm package "aave"

Boado emphasizes that the proposal isn’t an attack on Aave Labs but a clarification of ownership. "Aave Labs could still manage these assets in the future," he notes, "but the DAO must hold the keys."

Who Supports the Move?

Marc Zeller backs the proposal, stating: "Ownership should belong to the DAO, management can be delegated under binding terms, and monetization must align with AAVE token holders." Jordan Lazaro Gustave, Aave co-founder, has also voiced support. Notably, Boado suggests that entities with conflicts of interest abstain from voting—though the vote remains permissionless.

blockquote icon

What’s Next for Aave?

The proposal doesn’t require executable code, meaning a simple on-chain vote will decide. If passed, it could set a precedent for how DAOs assert control over their brands. For now, the community awaits the outcome, with many seeing this as a litmus test for decentralized governance.

FAQs: Aave DAO’s Brand Ownership Battle

What triggered the Aave DAO’s proposal?

The proposal followed Aave Labs redirecting $10M in annual fees away from the DAO treasury, sparking claims of privatization.

Who is leading the proposal?

Ernesto Boado, an independent contributor, drafted the plan, with backing from Marc Zeller and Jordan Lazaro Gustave.

Will Aave Labs lose all influence?

No—the proposal allows Aave Labs to retain management roles but transfers ultimate ownership to the DAO.

|Square

Get the BTCC app to start your crypto journey

Get started today Scan to join our 100M+ users

All articles reposted on this platform are sourced from public networks and are intended solely for the purpose of disseminating industry information. They do not represent any official stance of BTCC. All intellectual property rights belong to their original authors. If you believe any content infringes upon your rights or is suspected of copyright violation, please contact us at [email protected]. We will address the matter promptly and in accordance with applicable laws.BTCC makes no explicit or implied warranties regarding the accuracy, timeliness, or completeness of the republished information and assumes no direct or indirect liability for any consequences arising from reliance on such content. All materials are provided for industry research reference only and shall not be construed as investment, legal, or business advice. BTCC bears no legal responsibility for any actions taken based on the content provided herein.