Key Highlights
- Aave Labs proposes a two-part licensing framework for the canonical Aave V4 repositories.
- The system includes a Business Source License (BUSL) for the core codebase and a Contributor License Agreement (CLA) for contributors.
- Aave DAO will ultimately own the V4 intellectual property and codebase.
- The code will transition to open-source after a defined change date, likely within five years.
Aave Labs has introduced a governance proposal outlining a new licensing framework for the upcoming Aave V4 protocol repositories. The proposal introduces a two-part structure designed to standardize intellectual property ownership and community contributions as the protocol prepares for its next major upgrade.
Under the framework, the core V4 codebase will be licensed under the Business Source License (BUSL) while contributors will be required to sign a Contributor License Agreement (CLA) before submitting code.
According to the proposal, the goal is to create a licensing structure that is clear, enforceable, and consistent across the entire repository while supporting broader community participation in building the protocol.
The proposal is currently in the “Temp Check” stage, where community members discuss and evaluate the idea before it moves to governance voting.
BUSL license to protect the core protocol
The proposed BUSL license would govern the canonical Aave V4 repositories and their derivatives.
Under this framework, the Aave DAO would ultimately own the intellectual property rights of the V4 codebase, while Aave Labs would temporarily hold licensing authority during development to protect the protocol until governance processes are finalized.
The proposal also suggests restructuring the repository using SPDX license identifiers at the file level, allowing developers to clearly identify which license applies to each part of the codebase.
This approach is designed to prevent fragmentation as more contributors build on the protocol’s modular V4 architecture.
Code will become open source after “Change Date”
Consistent with previous Aave releases, the V4 code will transition to an open-source license after a defined “Change Date.”
The proposal suggests that this change could occur within five years of the protocol’s deployment, though the exact timing would be recorded in the repository metadata.
The licensing approach mirrors the model used for Aave V3, where the code is initially protected before eventually becoming fully open source.
Contributor license agreement introduced
In addition to the BUSL license, developers contributing to the V4 codebase would need to sign a Contributor License Agreement (CLA).
The CLA does not transfer ownership of the contributor’s work. Instead, it grants the community an irrevocable right to use, integrate, and sublicense the contribution as part of the protocol.
The proposal argues that such agreements eliminate legal ambiguity and ensure that the entire codebase operates under a consistent licensing framework.
Next steps in governance
The licensing framework is currently undergoing community discussion. If consensus is reached during the Temp Check stage, the proposal will move through the following governance steps:
- Snapshot vote for community signaling
- ARFC stage for refinement
- Final snapshot approval
- Transfer of V4 intellectual property and repository control to the Aave DAO
The licensing framework is expected to be finalized before the production release of Aave V4, the protocol’s next major upgrade aimed at expanding modular DeFi lending infrastructure.
Also Read: Hyperliquid Plans Upgrade to Boost Leverage for Experienced Traders
