September Funding Update - Part A
01Summary
Multi-chain treasury rebalancing proposal: migrate Aave v2 assets to v3 on Polygon, consolidate holdings from Polygon/Arbitrum/Optimism to Ethereum, rescue Paraswap funds, reimburse Guardian signer funding (0.264 ETH to karpatkey), swap various assets to GHO on Ethereum, and allocate 3M GHO and 800 aEthWETH to Merit and Ahab programs.
- Type
- treasury allocation
Key changes
- Migrate all amUSDT, amDAI, amWMATIC, amWETH, amWBTC, and amLINK from Aave v2 to v3 on Polygon(high)
- Withdraw aUSDC and aLUSD from Polygon, Arbitrum, and Optimism and transfer to Ethereum(high)
- Rescue Paraswap adapter contract funds across Ethereum, Polygon, Optimism, and Arbitrum(high)
- Swap approximately 1.25M aUSDC, 1.25M aUSDT, and all DAI, aDAI, aEthDAI, aLUSD, LUSD, FRAX, aFRAX on Ethereum to GHO(high)
- Create allowances to Merit and Ahab programs: 3M GHO and 800 aEthWETH from Aave v3 Ethereum(medium)
- Reimburse karpatkey 0.264 ETH for Guardian signer funding(low)
Generated by Kvorum
02Description
Simple Summary
This AIP will migrate funds from Aave v2 to v3 on Polygon, withdraw funds from Polygon, Arbitrum and Optimism to Ethereum, rescue Paraswap funds. This AIP also executes for reimbursing for the funding of Guardian signers, and create allowances to the Merit and Ahab.
Motivation
As part of our ongoing Treasury asset rebalancing, this proposal when implemented will continue the migration of assets from v2 instances of Aave to v3. In response to recent events, funds currently locked in the Paraswap adapter contracts will be send to the DAOs Treasury. Due to size of these holding, this will only be performed on Polygon, Optimism, Ethereum and Arbitrum where this proposal is already intending updating the DAOs holdings.
Specification
Migrate the following assets from Aave v2 to v3 Polygon.
amUSDT (All-100x10^6) amDAI (All-1.0x10^18) amWMATIC (All-1.0x10^18) amWETH (All-1.0x10^18) amWBTC (All-1.0x10^8) amLINK (All-1.0x10^18)
Transfer the following assets to Ethereum.
| Polygon | Arbitrum | Optimism |
|---|---|---|
| amUSDC.e (All-100x10^6) | aArbUSDC (All-100x10^6) | aOptUSDC (All-100x10^6) |
| aPolUSDC (All-100x10^6) | aArbLUSD (All-1.0x10^18) | aOptLUSD (All-1.0x10^18) |
Rescue Paraswap Funds
Rescue funds held in the Paraswap adapter contracts and send back to Treasury in line with this PR 454 on Ethereum.
Gas Rebate
Transfer 0.264 ETH to 0x818C277dBE886b934e60aa047250A73529E26A99 (karpatkey) reimbursing for the funding of Guardian signers.
Swap funds to GHO
| Ethereum |
|---|
| aUSDC (1.25M) |
| aUSDT (1.25M) |
| DAI (All) |
| aDAI (All-1.0x10^-18) |
| aEthDAI (0.5M) |
| aLUSD (All-1.0x10^-18) |
| LUSD (All) |
| FRAX (All) |
| aFRAX (All-1.0x10^-18) |
Merit + Ahab Programs
Create allowances to the Merit and Ahab, 3M GHO and 800 aEthWETH from Aave v3 Ethereum: SAFE: 0xdeadD8aB03075b7FBA81864202a2f59EE25B312b
References
- Implementation: AaveV3Ethereum, AaveV3Polygon, AaveV3Optimism, AaveV3Arbitrum
- Tests: AaveV3Ethereum, AaveV3Polygon, AaveV3Optimism, AaveV3Arbitrum
- Snapshot: Direct-to-AIP
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The decoded on-chain data consists of a single generic execute() call to an Ethereum payload contract with no arguments decoded beyond the fallback signature. This is the standard pattern for Aave governance proposals of this type: the actual multi-chain logic (Aave v2->v3 migration on Polygon, cross-chain transfers from Polygon/Arbitrum/Optimism to Ethereum, Paraswap rescue, gas rebate transfer, GHO swaps, and Merit/Ahab allowances) is encoded inside the payload contract's own bytecode/logic, which is executed via delegatecall or internal calls not surfaced as separate decoded actions here. Because the calldata trace only exposes a single opaque execute() call, there is no way to verify or contradict the specific amounts, addresses, or asset lists claimed in the description at the calldata level provided. I found no evidence of a mismatch, but I also cannot confirm the granular claims (e.g., 0.264 ETH amount, 3M GHO allowance, specific asset transfers) against the calldata. Given this limited visibility, confidence is low rather than asserting a discrepancy - per guidance, low-confidence findings should not be treated as warnings. Overall the available data does not contradict the description, so I mark this consistent with low confidence rather than flagging unverifiable specifics as discrepancies.
Generated by Kvorum
04Actions
- Target
- 0xc554…4c18
- 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
- aaveexecutedFebruary Funding Update - Part B92%
- aaveexecutedMay Funding Update91%
- aaveexecutedMay Funding Update90%
- aaveexecutedFebruary Funding Update (Part 1)90%
- aaveexecutedSeptember Funding Update90%
- aavecanceledMay Funding Update89%
- aaveexecutedApril Funding update88%
- aaveexecutedNovember Funding Update88%
- aavecanceledSeptember Funding Update88%
- aaveexecutedJuly 2025 - Funding Update87%