Aave Will Win Framework: Primary Funding Request
01Summary
Aave DAO governance proposal to fund Aave Labs through the Aave Will Win Framework Primary grant component with $25,000,000 in stablecoins (aEthLidoGHO) distributed through streams over 6-12 months, plus 75,000 AAVE tokens vesting linearly over 4 years. This shifts revenue responsibility from Aave Labs to the DAO treasury. Any unspent funds after 12 months return to treasury.
- Type
- treasury allocation
- Funding
- $25000000
Key changes
- Allocate $25,000,000 in stablecoins (aEthLidoGHO) to Aave Labs through multiple streams: $5M immediate allowance, $5M streamed over 6 months, $15M streamed over 12 months(high)
- Allocate 75,000 AAVE tokens to Aave Labs vesting linearly over 48 months from Ecosystem Reserve(high)
- Shift revenue from Aave-branded products from Aave Labs to DAO treasury, making DAO responsible for funding Aave Labs activities(high)
- Any unspent Primary grant portion after 12-month period returned to DAO treasury or handled through subsequent DAO-approved budget decision(medium)
Notable concerns
- This proposal only covers the Primary grant component; Growth and Development grants from the broader Aave Will Win Framework will be handled through separate governance proposals
- Unspent funds have conditional return mechanism requiring future DAO decision
Generated by Kvorum
02Description
Simple Summary
This AIP proposes to approve the primary grant component of the Aave Will Win Framework as a standalone governance action.
If approved, the Aave DAO would fund Aave Labs through various grants consisting of $25,000,000 in stablecoins in totality, alongside a 75,000 AAVE token allocation vesting linearly over four years.
This AIP is limited to the funding request and its full onchain execution. Other elements of the broader framework, including the Growth and Development grants, are intended to be handled through separate governance proposals.
Motivation
Under the proposed operating model, revenue generated by Aave-branded products would flow to the DAO treasury rather than being retained by Aave Labs. As described in the source proposal, this shifts responsibility for funding Aave Labs’ activities to the DAO.
Specification
This proposal approves funding of the Primary grant of $25,000,000 in stablecoins, and 75,000 AAVE to Aave Labs, structured as follows:
- Allowance for 5M units aEthLidoGHO from the Collector Contract
- Stream for 5M units aEthLidoGHO from the Collector Contract over 6 month duration
- Stream for 15M units aEthLidoGHO from the Collector Contract over 12 month duration
- Stream for 75,000 units AAVE from the Ecosystem Reserve over 48 month duration
Any unspent portion of the Primary grant at the end of the 12-month period shall be returned to the DAO treasury or otherwise handled through a subsequent DAO-approved budget decision.
The Aave Labs recipient address is: 0x488c053F07391dC78b12Da7107eb22aF77A255a1.
The specification has been taken in consultation with Token Logic, the treasury service provider of the DAO.
References
- Implementation: AaveV3EthereumLido
- Tests: AaveV3EthereumLido
- Snapshot
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal describes a multi-part funding package (an allowance and two GHO streams from the Collector, plus a 4-year AAVE vesting stream from the Ecosystem Reserve, to a named recipient). However, the decoded on-chain action is a single opaque execute() call to a payload contract address, with no arguments decoded. This is the standard pattern for Aave V3 governance payloads, where the granular logic (amounts, recipients, durations) lives in the payload contract's bytecode rather than in the top-level calldata. Because the calldata gives no directly comparable figures, addresses, or durations, I cannot verify or contradict the specific dollar amounts, token amounts, vesting periods, or recipient address stated in the description. Nothing in the visible calldata conflicts with the description, but the granular claims are unverifiable from what's provided. Given the reference to a specific, named implementation contract (AaveV3EthereumLido_AaveWillWinFrameworkPrimaryFundingRequest) matching the target address pattern typical of this governance framework, there is no indication of malfeasance, but confidence in a full match must be low since the actual sub-actions are not decoded. I am marking this consistent with low confidence rather than flagging discrepancies, since no data contradicts the description — the limitation is in calldata visibility, not in a detected mismatch.
Generated by Kvorum
04Actions
- Target
- 0x59f1…b63e
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedAave Events & Sponsorship Budget 202580%
- aaveexecutedRenew Aave Grants DAO78%
- aaveexecutedAave BGD Phase 577%
- aaveexecutedAave Grants DAO77%
- aaveexecutedAave BGD Phase 477%
- aaveexecutedRenew Aave Grants DAO77%
- aaveexecutedEvents Grant 202476%
- aaveexecutedAave BGD Phase 276%
- aaveexecutedAL Service Provider Proposal76%
- aaveexecutedAave BGD Phase 6 & Project E agreement76%