Aave Labs has proposed creating an independent Cayman Islands foundation to hold and protect the trademarks, domains, code-related intellectual property and other legal assets associated with the Aave Protocol, addressing a structural problem common to decentralized organizations: the DAO can vote on protocol matters but cannot itself own property or bring legal claims.
The proposal is currently in Aave’s Request for Comment, or ARFC, stage. If it gains community support, it would move to a non-binding Snapshot vote and then to an onchain Aave Improvement Proposal, or AIP, covering incorporation and initial operating costs. Each subsequent stage of asset transfers would return to governance for separate approval.
Under the proposed structure, the Aave Foundation would be incorporated as a memberless foundation company under the Cayman Islands Foundation Companies Act. Its charter would limit it to holding, safeguarding and licensing intellectual property for the Aave Protocol. It would not receive authority over listings, risk parameters, budgets, service-provider selection or other protocol decisions that remain under token-holder governance.
A legal owner for protocol assets
Aave Labs’ proposal argues that the DAO currently pays for assets it cannot legally own or defend. DAOs do not generally have legal personality in the way companies or foundations do, creating difficulties when they need to register trademarks, control domain names, sign intellectual-property assignments or pursue infringement claims.
The new entity would take legal ownership of Aave trademarks, main domain names, intellectual property in transferred protocol code repositories, and rights created under service-provider agreements. It would be responsible for registering and maintaining those assets, managing their licensing and pursuing legal measures when required to protect them.
That arrangement would give the protocol a standing legal vehicle for brand and intellectual-property administration without turning the foundation into an operating company or a second governance body. The distinction is central to the proposal: token holders would continue to decide what work is commissioned, who performs it and how contributors are paid, while the foundation would receive ownership of the work once it is delivered under the agreed terms.
The proposal says ownership of work commissioned by the DAO has been handled inconsistently. Code, risk-management tools, financial models and documentation developed by external service providers may be governed by different agreements, and some intellectual property has remained with the provider that created it.
Future service-provider agreements would include an intellectual-property transfer requirement under the plan. Those terms would be added as existing agreements are renewed or providers are replaced through Aave’s normal governance process. The foundation would not choose providers, direct development work or determine the scope of DAO-funded projects.
Independent director subject to DAO removal
The planned foundation would be managed by an independent director and overseen by an independent supervisor. The supervisor could not have a relationship with the director, a safeguard intended to prevent the foundation’s day-to-day legal administration from being controlled by a single connected group.
After the initial appointments, the director could only be appointed or removed through an AIP. Aave Labs, DAO-hired service providers and their affiliates would be prohibited from appointing either the director or supervisor, and they would also be barred from holding those positions themselves.
The DAO would retain several hard controls over the foundation through governance. Token holders could instruct the entity to liquidate and transfer its remaining assets to a successor organization. Amendments to the foundation’s charter, the disposal of core intellectual property, mergers and reorganizations would also require DAO consent.
Those limits are designed to prevent the legal wrapper from accumulating discretion over the protocol itself. The foundation would have no voting rights, veto rights or formal consultation role in decisions involving Aave markets, treasury allocations, parameter changes, listings or service-provider budgets.
Free brand licensing for Aave builders
The proposal also sets out a licensing model for the Aave name and related trademarks. Builders would receive a one-way authorization to use Aave branding for Aave-branded products without paying licensing fees, subject to the foundation’s role in protecting the marks.
A trademark holder needs to monitor use of its marks to avoid confusion and preserve the ability to enforce its rights. Centralizing that responsibility in a foundation could make it easier for the Aave ecosystem to distinguish official or authorized products from unaffiliated services using similar names or branding.
The proposal frames the foundation as a custodian rather than a commercial licensing operation. It would not charge builders for brand permission under the suggested arrangement, and it would not claim control over the protocol’s technical or financial governance.
For Aave, the model would place brand protection and code-repository ownership in a dedicated entity while preserving the DAO’s control over the economic and technical decisions that shape the lending protocol.
Costs require a separate governance process
The DAO would pay reasonable costs associated with setting up the foundation, hiring a qualified company secretary, completing legal work and transferring trademarks and intellectual property. The ARFC does not seek a recurring operating budget.
Any request for ongoing funding would need to be submitted as a separate governance proposal, giving token holders another opportunity to review spending after the entity has been established. The foundation would also be required to publish quarterly reports to the Aave governance forum.
Those reports would cover the assets held by the foundation, changes in ownership, operating expenses and legal actions involving the protection of trademarks or code repositories. The first report would be due within 90 days of the end of the first full calendar quarter after the foundation begins operating.
The phased approach means incorporation would not automatically complete every transfer. Following an AIP approving formation costs and the appointment of an independent director and supervisor, the initial planned transfers would cover Aave trademarks, main domains and relevant protocol code-repository rights. Later implementation steps would be separately proposed to the governance forum.
The proposal therefore gives the Aave DAO a route to formalize ownership of assets created around the protocol without changing who controls the protocol’s rules. Its progress now depends on whether the community accepts the Cayman foundation as the appropriate legal holder and approves the costs needed to establish it.
Want deeper context on decentralized governance and compliance? Explore our guide on what DAOs are and how they work today.
Disclaimer: The content on this page is provided for general informational purposes only and does not represent the views or financial advice of Toobit. We make no guarantees regarding the accuracy or completeness of this information and shall not be held liable for any errors, omissions, or outcomes resulting from its use. Investing in digital assets involves risk; users should independently evaluate their financial situation and the risks involved. For further details, please consult our Terms of Service and Risk Disclosure.
