December Funding Update
01Summary
December Funding Update to acquire 2M GHO for runway, deposit idle ETH into Aave v3 Prime, expand AFC and Ahab SAFE remits to support GHO liquidity by creating allowances for stkAAVE, aEthLidoWETH, AAVE, expired Principle Tokens, and 3M aEthLidoGHO for the Merit program.
- Type
- treasury allocation
Key changes
- Acquire 2M GHO via MainnetSwapSteward to be deposited into Aave v3 Prime instance(high)
- Deposit idle ETH from Ethereum Collector into Aave v3 Prime instance(high)
- Replenish MainnetSwapSteward budgets: 2M USDC, 4M USDT, 2M USDS(high)
- Create allowance for all stkAAVE to be transferred to AFC for redemption and GHO borrowing(high)
- Approve 2,300 aEthLidoWETH transfer to Ahab SAFE for GHO collateral(high)
- Approve 20,000 AAVE to AFC for future buyback movements(medium)
- Approve expired Principle Tokens redemption to AFC for conversion to GHO(medium)
- Approve 3,000,000 aEthLidoGHO to Merit program for distribution(high)
Notable concerns
- Transition to MainnetSwapSteward for buybacks represents operational change
- Large allowances created (20,000 AAVE larger than current balance) to facilitate future movements
- Use of Prime instance deposits and collateral borrowing for GHO liquidity
- Expired Principle Tokens need conversion handling
Generated by Kvorum
02Description
Simple Summary
This publication presents the December Funding Update, consisting of the following key activities:
- Acquire GHO to support runway;
- Expand the remit of the AFC & Ahab SAFEs to support GHO liquidity; and
- Create allowances to support operations.
Motivation
Specification
Runway
Using the MainnetSwapSteward and the already approved allowances, acquire 2M GHO to be deposited into the Prime instance.
Replenish the budgets on the MainnetSwapSteward, as they will be consumed by the rebalancing of assets mentioned above.
- USDC: 2M increase
- USDT: 4M increase
- USDS: 2M increase
Collector Assets
Deposit idle ETH held on the Ethereum Collector into the Prime instance of Aave v3.
Create allowances for the following assets to be transferred from the Treasury to the AFC, where stkAAVE will be redeemed for AAVE and held on the AFC SAFE.
Amount: All stkAAVE
Spender: AFC 0x22740deBa78d5a0c24C58C740e3715ec29de1bFa
Method: approve() stkAAVE on the Aave Collector contract to the AFC address.
Amount: 2,300 aEthLidoWETH
Spender: Ahab 0xAA2461f0f0A3dE5fEAF3273eAe16DEF861cf594e
Method: approve() aEthLidoWETH on the Aave Collector contract to the ahab address
Note: To support ongoing DEX liquidity, launching GHO on Plasma and other networks, this publication grants the Aave Finance Committee (AFC) ability to provide DEX liquidity and reduce the reliance on incentive distribution. These assets now held in the AFC and Ahab SAFEs will be used as collateral to borrow GHO and fund the DEX liquidity.
Amount: 20,000 AAVE
Spender: AFC 0x22740deBa78d5a0c24C58C740e3715ec29de1bFa
Method: approve() AAVE on the Aave Collector contract to the AFC address
Note: We have transitioned to using the MainnetSwapSteward for buybacks, with the acquired AAVE going directly to the collector, thus we'll create an allowance enabling the AAVE acquired to be held on the AFC SAFE. The Allowance is larger than the current balance to facilitate future buyback movements.
Redeem expired Principle Tokens to the underlying and convert to GHO.
Amount: 175.190155978359917557 PT_eUSDe_14AUG2025
Amount: 3,043.54299785406069585 PT_sUSDE_25SEP2025
Amount: 1,583.144136895510331668 aEthPT_USDe_31JUL2025
Spender: AFC 0x22740deBa78d5a0c24C58C740e3715ec29de1bFa
Method: approve() on the Aave Collector contract to the AFC address
Merit Program
Asset: 3,000,000 aEthLidoGHO
Spender: Merit 0xdeadD8aB03075b7FBA81864202a2f59EE25B312b
Method: approve() aEthLidoGHO on the Aave Collector contract to the Merit address
References
- Implementation: AaveV3Ethereum
- Tests: AaveV3Ethereum [Snapshot] Direct-to-AIP
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The decoded on-chain data contains only a single top-level action: a call to execute() on what appears to be the proposal's payload contract address, consistent with Aave's standard governance pattern where a single payload contract performs multiple internal operations (approvals, swaps, deposits) via delegatecall. The actual sub-actions described in the proposal text (GHO acquisition, budget replenishment, various token approvals to AFC/Ahab/Merit) are not individually visible in the provided decoded calldata — they would be encoded inside the payload contract's bytecode, which is not included here. Because only this single generic execute() call is available for comparison, I cannot verify or refute the specific amounts, targets, or approvals claimed in the description against the actual sub-calls. This is a normal and expected pattern for Aave 'Direct-to-AIP' proposals, so I do not treat the lack of visible sub-actions as a discrepancy, but confidence in a detailed comparison is necessarily low given the limited decoding depth provided.
Generated by Kvorum
04Actions
- Target
- 0x4c87…5111
- 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.