Aave BGD Phase 4
01Summary
Aave DAO proposes a 6-month service engagement with BGD Labs (October 1, 2024 - April 1, 2025) for development, security, and technical maintenance. Total compensation: 2.3M aUSDC and 5,000 AAVE tokens, split 50/50 between upfront payment and streaming payments.
- Type
- treasury allocation
- Funding
- $2,300,000
Key changes
- Upfront transfer of 1,150,000 aUSDC (v3 Ethereum) from Aave DAO treasury to BGD Labs(high)
- Upfront transfer of 2,500 AAVE tokens from Aave Ecosystem Reserve to BGD Labs(high)
- Creation of payment stream for 1,150,000 aUSDC from execution until April 1, 2025(high)
- Creation of payment stream for 2,500 AAVE tokens from execution until April 1, 2025(high)
Generated by Kvorum
02Description
Simple Summary
Proposal for an engagement of development and security services between the Aave DAO and BGD Labs, from 1st October 2024 until 1st April 2025.
Motivation
For the last two and a half years, BGD Labs has been a service provider of the Aave DAO, contributing with multiple developments, technical maintenance, and security coordination tasks.
The motivation/goal of this new engagement is:
- Keep the stability and trust in the Aave technology.
- Innovate responsibly on production systems.
- Support all other non-tech contributors to the DAO, accelerating progress.
In summary, the same as before, but always striving for better.
Specification
A full description of the scope can be found on the Aave Governance Forum HERE or on the pre-approval on ARFC (Aave Request For Comments) HERE.
In terms of implementation, this proposal sets up the payment schedule defined:
- From the Aave DAO's treasury (Collector smart contract), an upfront transfer for a value of 1'150'000 aUSDC (v3 Ethereum), 50% of the stablecoins budget.
- From the Aave DAO AAVE Ecosystem Reserve, an upfront transfer for a value of 2'500 AAVE tokens, 50% of the tokens budget.
- From the Aave DAO's treasury, the creation of a payment stream for a value of 1'150'000 aUSDC (v3 Ethereum), from the execution time of this proposal until 1st April 2025, completing the 6-month duration, for the other 50% of the stablecoins budget.
- From the Aave DAO AAVE Ecosystem Reserve, the creation of a payment stream for a value of 2'500 AAVE tokens, from the execution time of this proposal until 1st April 2025, completing the 6-month duration, for the other 50% of the tokens budget.
The approval of this proposal by Aave governance acts as a binding agreement between the Aave DAO and BGD Labs. Detailed terms of service can be found HERE.
References
- Implementation: AaveV3Ethereum
- Tests: AaveV3Ethereum
- Snapshot
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal follows Aave's standard governance execution pattern: the on-chain action is a single call to execute() on a payload contract address, which matches the linked implementation contract (AaveV3Ethereum_AaveBGDPhase4) referenced in the description's 'References' section. The actual transfers of aUSDC and AAVE tokens, plus the creation of payment streams, are encoded inside that payload contract's bytecode and are not directly visible in the decoded top-level calldata provided here. Because only the outer execute() call is decoded, I cannot independently verify the specific amounts (1,150,000 aUSDC upfront + stream, 2,500 AAVE upfront + stream) against on-chain state — this is a common limitation when reviewing Aave payload-based proposals rather than raw multi-action calldata. No contradiction was found between the description and what is visible on-chain (the target contract matches the linked implementation), so I did not identify a discrepancy, but confidence is low because the calldata visible does not allow line-by-line verification of the amounts and recipients claimed in the prose. Delegates relying on this analysis should also review the linked Solidity payload source and forum scope document directly to confirm the four claimed transfers/streams are correctly implemented, since this is standard practice for Aave DAO proposals and no red flags were observed in the visible calldata pattern.
Generated by Kvorum
04Actions
- Target
- 0x84b9…5a99
- 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 BGD Phase 599%
- aaveexecutedAave BGD Phase 293%
- aaveexecutedAave BGD Phase 6 & Project E agreement93%
- aaveexecutedAave BGD Phase 390%
- aaveexecutedApproval of BGD contribution to Aave86%
- aaveexecutedAL Service Provider Proposal81%
- aaveexecutedAave Will Win Framework: Primary Funding Request77%
- aaveexecutedAave Events & Sponsorship Budget 202575%
- aaveexecutedEvents Grant 202474%
- aaveexecutedEvents Funding74%