Aave treasury RWA Allocation Part I
01Summary
Aave DAO proposes to allocate 50k USDC and 500 AAVE tokens to Centrifuge over two years to explore Real World Asset (RWA) investment opportunities and generate recurring treasury revenue through off-chain US treasury asset financing.
- Type
- treasury allocation
- Funding
- $50000
Key changes
- Withdraw 50k aUSDC from Aave COLLECTOR contract, convert to USDC, and transfer to Centrifuge Treasury(high)
- Create 500 AAVE token stream to Centrifuge Treasury over two years(high)
- Begin Aave DAO's RWA allocation strategy and develop internal RWA expertise(high)
Notable concerns
- Centrifuge Prime is a new investment vehicle requiring DAO familiarization with RWA processes
- Success of this allocation depends on achieving projected 5% returns on US treasury assets to generate estimated $250k annual recurring revenue
Generated by Kvorum
02Description
Simple Summary
This proposal is the first part of the Aave treasury RWA allocation. It proposes to allocate 50k USDC & 500 AAVE to Centrifuge.
Motivation
Aave has long been a contributor and supporter of RWA initiatives. Since the first announcement of GHO, the Aave community has consistently expressed its interest in expanding into this area. Treasury Management at Aave has historically been focused on strategic crypto assets, ignoring the returns and liquidity available in offchain markets for various reasons.
Today, with roughly 17% of the treasury in stablecoins (~13m USD), the Aave DAO is overlooking the 5% available interest in the risk-free rate of overnight financing of US treasury assets. This can offer $250,000 of recurring revenue a year at just 5m USD of investment. These markets can immediately become some of the highest earning revenue streams for the DAO.
Beyond just economics, this proposal would allow the Aave DAO to establish and begin developing the internal RWA expertise necessary to engage with these markets. Centrifuge Prime is purpose-built for DeFi native organizations, offering the critical services and infrastructure necessary to onboard a diverse portfolio of RWA through a single interface.
Centrifuge has a long track record of working with DAOs to bring RWA on as collateral, and pioneered the first Aave deployment into RWA with the joint development of the RWA Market. Onboarding Aave to Centrifuge Prime for liquid investment strategies is an optimal approach for scaling RWA with the Aave community. It will develop the legal and technical infrastructure necessary to interface with RWAs safely and efficiently, while allowing the Aave community to get comfortable and familiar with the processes and thinking around RWA. This will put Aave in a significantly improved position to be able to leverage RWA collateral for GHO in the long term, either to improve liquidity or develop additional revenue streams.
Specification
This proposal withdraws 50k aUSDC from the Aave COLLECTOR contract and converts them to USDC before transferring them to the Centrifuge Treasury. This proposal also create a 500 AAVE stream for a period of two years to the Centrifuge Treasury.
References
- Implementation: Ethereum
- Tests: Ethereum
- Snapshot
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal follows the standard Aave governance execution pattern: the on-chain action is a single call to execute() on a payload contract, which is the conventional mechanism used by Aave governance proposals (as referenced by the linked Solidity implementation file). The actual granular logic — withdrawing 50k aUSDC, converting to USDC, transferring to the Centrifuge Treasury, and creating a 500 AAVE two-year stream — is expected to live inside that payload contract's bytecode, which is not visible in the decoded action list provided (only the outer execute() call is decoded). Because no inner calls, amounts, or recipient addresses are exposed in the decoded calldata, I cannot directly verify the 50k USDC and 500 AAVE figures or the Centrifuge Treasury address against on-chain data. However, this opacity is typical of Aave's payload-based governance architecture and is not itself a red flag — proposals of this type are routinely audited via the linked source code rather than the raw calldata trace. There is no evidence in the available decoded data that contradicts the description, so I do not flag any value, target, or omission discrepancies. Confidence is medium rather than high because the single execute() call prevents full independent verification of the specific amounts and recipient claimed in the prose.
Generated by Kvorum
04Actions
- Target
- 0xfd69…6f75
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 320x329c…3ed4 | For | 108.3K | 17.05% | — | 3y ago |
| 070x0703…961b | For | 88.1K | 13.87% | — | 3y ago |
| 620x62a4…816a | For | 62.4K | 9.82% | — | 3y ago |
| 130x13bd…8548 | For | 61.3K | 9.65% | — | 3y ago |
| 230x2331…7e73 | For | 60K | 9.45% | — | 3y ago |
| 730x732a…b848 | For | 49K | 7.72% | — | 3y ago |
| EA0xea17…6676 | For | 46.6K | 7.34% | — | 3y ago |
| B90xb933…8dd1 | For | 42K | 6.62% | — | 3y ago |
| EZezr3al.eth0x8659…7d0e | For | 37.8K | 5.94% | — | 3y ago |
| 2C0x2cc1…4df1 | For | 28K | 4.41% | — | 3y ago |
| 570x57ab…2922 | For | 24.7K | 3.89% | — | 3y ago |
| E40xe459…e666 | For | 20K | 3.15% | — | 3y ago |
| 180x1855…98ba | For | 5K | 0.79% | — | 3y ago |
| 870x8787…ea52 | For | 1.1K | 0.18% | — | 3y ago |
| 3A0x3a25…e9d2 | For | 300 | 0.05% | — | 3y ago |
| 5A0x5acb…eedf | For | 282 | 0.04% | — | 3y ago |
| DF0xdf06…4977 | For | 27.3 | 0.00% | — | 3y ago |
| 460x46a9…901b | For | 26.1 | 0.00% | — | 3y ago |
| AF0xaf5c…4d51 | For | 17.8 | 0.00% | — | 3y ago |
| 680x680a…5d5f | For | 2.7 | 0.00% | — | 3y ago |
| A70xa772…6171 | For | 2.1 | 0.00% | — | 3y ago |
| 400x40df…1e39 | For | 1.3 | 0.00% | — | 3y ago |
| 010x0151…c3b9 | For | 1.2 | 0.00% | — | 3y ago |
| 4C0x4cc8…741a | For | 1.2 | 0.00% | — | 3y ago |
| 000x0034…a298 | For | 1.1 | 0.00% | — | 3y ago |
| 2B0x2ba0…8412 | For | 1.1 | 0.00% | — | 3y ago |
| C70xc724…b01d | For | 1 | 0.00% | — | 3y ago |
| 740x74a2…c125 | For | 1 | 0.00% | — | 3y ago |
| 850x85d5…8993 | For | 1 | 0.00% | — | 3y ago |
| B80xb8fb…677f | For | 1 | 0.00% | — | 3y ago |
| 550x5505…3e23 | For | 0.8 | 0.00% | — | 3y ago |
| 360x3647…a20e | For | 0.8 | 0.00% | — | 3y ago |
| 5B0x5bf7…29aa | For | 0.7 | 0.00% | — | 3y ago |
| 420x421c…b31f | For | 0.3 | 0.00% | — | 3y ago |
| 280x28d9…8151 | For | 0.3 | 0.00% | — | 3y ago |
| 180x189d…0697 | For | 0.3 | 0.00% | — | 3y ago |
| 090x0927…1922 | For | 0.3 | 0.00% | — | 3y ago |
| DE0xdefe…39bb | For | 0.2 | 0.00% | — | 3y ago |
| D30xd36b…65ba | For | 0.2 | 0.00% | — | 3y ago |
| 620x621b…82e0 | For | 0.2 | 0.00% | — | 3y ago |
| 460x46e7…b87f | For | 0.2 | 0.00% | — | 3y ago |
| 150x1557…a892 | For | 0.2 | 0.00% | — | 3y ago |
| D40xd4ee…6795 | For | 0.2 | 0.00% | — | 3y ago |
| 610x61bf…ac0d | For | 0.2 | 0.00% | — | 3y ago |
| 7D0x7d55…b6f6 | For | 0.1 | 0.00% | — | 3y ago |
| E70xe77e…60a4 | For | 0.1 | 0.00% | — | 3y ago |
| 860x8671…5c0a | For | 0.1 | 0.00% | — | 3y ago |
| DB0xdb29…de23 | For | 0.1 | 0.00% | — | 3y ago |
| 160x16a1…b354 | For | 0.1 | 0.00% | — | 3y ago |
| 300x304e…ebec | For | 0.1 | 0.00% | — | 3y ago |
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedEnhancing Aave DAO’s Liquidity Incentive Strategy on Balancer74%
- aaveexecutedintroduce Liquidity Incentives for Aave v273%
- aaveexecutedaAMPL Second Distribution73%
- aaveexecutedInterim aAMPL distribution72%
- aaveexecutedExtend Liquidity Incentives for Aave v270%
- aaveexecutedAave V2 - Liquidity Mining Program (90 days at 30% reduced rate)70%
- aaveexecutedAave V2 - Liquidity Mining Update (90 days at 30% reduced rate)69%
- aaveexecutedwstETH CAPO Oracle Incident User Reimbursement68%
- aaveexecutedClaiming AAVE Rewards for the Sablier Legacy v1.1 Contract66%
- aaveexecutedWhitelist Balancer’s Liquidity Mining Claim66%