June Funding Update - Part II
01Summary
June Funding Update proposal to acquire 3M GHO through swaps of 1M USDT and 2M USDC, establish 6M USD allowance for AAVE buybacks (4M aEthUSDT + 2M aEthUSDC), and fund Merit program with 3M aEthLidoGHO and Ahab program with 800 aEthWETH through November.
- Type
- treasury allocation
- Funding
- $6M
Key changes
- Swap 1M USDT and 2M USDC for 3M GHO to support DAO operations(high)
- Create 4M aEthUSDT and 2M aEthUSDC allowance for Aave Finance Committee to execute 6 weeks of AAVE buybacks(high)
- Allocate 3M aEthLidoGHO to Merit program, funding operations through beginning of November(high)
- Allocate 800 aEthWETH to Ahab program for continued distribution through next budget period(medium)
Notable concerns
- Merit funding extends only until beginning of November, requiring future proposals for continued support
- Ahab ETH allocation subject to price fluctuations; previous period's 800 ETH budget was not fully consumed
Generated by Kvorum
02Description
Simple Summary
This publication presents the June Funding Update, consisting of the following key activities:
- Acquire 3M GHO for Operations;
- Continue AAVE buybacks for 6 weeks; and,
- Create Merit & Ahab Allowances.
Motivation
This publication focuses on supporting near term operational funding requirements.
Acquire GHO
In the short term, we anticipate multiple initiatives will seek funding from the DAO. This proposal, once enacted, will secure a sufficient amount of GHO to support the DAO’s operations. This ensures the DAO remains consistently well-capitalized.
Upcoming anticipated expenses include:
- Renewal of Service Provider agreements, eg: Chaos Labs;
- Create 6M USD Allowance for AAVE buybacks; and,
- Future Merit and ALC distributions up until November; and,
- Incentive campaign(s).
Fund Merit + Ahab Programs
Merit is $12M per year at 3M per quarter or 1M per month. Merit is currently funded up until end of July. With the implementation of this proposal, Merit will be funded until beginning of November.
Ahab is $8M per year with the amount of ETH being distributed subject to ETH price fluctuations. The previous 3 month period’s budget was 800 ETH and of this 800 ETH, not all has been consumed. As a result, the next budget period will receive only 800 ETH.
Specification
Perform the following swaps:
| Token | Amount | Acquire |
|---|---|---|
| USDT | 1.00M | GHO |
| USDC | 2.00M | GHO |
Create Allowances
AAVE Buybacks
Create a 4M aEthUSDT and 2M aEthUSDC allowance for the Aave Finance Committee to perform 6 weeks of AAVE buybacks.
Asset: aEthUSDT 0x23878914EFE38d27C4D67Ab83ed1b93A74D4086a
Amount: 4M
Asset: aEthUSDC 0x98C23E9d8f34FEFb1B7BD6a91B7FF122F4e16F5c
Amount: 2M
Spender: AFC 0x22740deBa78d5a0c24C58C740e3715ec29de1bFa
Method: approve() aEthUSDT and aEthUSDC on the Aave Collector contract to the AFC address.
Merit + Ahab Programs
Create allowances to the Merit and Ahab, 3M aEthLidoGHO and 800 aEthWETH from Aave v3 Prime and Core respectively on Ethereum:
Asset: aEthLidoGHO: 0x18eFE565A5373f430e2F809b97De30335B3ad96A
Amount: 3M
Asset: aEthWETH: 0x4d5F47FA6A74757f35C14fD3a6Ef8E3C9BC514E8
Amount: 800
Spender: Merit 0xdeadD8aB03075b7FBA81864202a2f59EE25B312b Method: approve() aEthLidoGHO and aEthWETH 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 proposal description makes several specific, verifiable claims: two token swaps (USDT→GHO, USDC→GHO), and three approve() allowances (to AFC for AAVE buybacks, and to Merit for Merit/Ahab funding) with specific token addresses and amounts. However, the decoded on-chain action list contains only a single generic execute() (fallback) call to what appears to be an Aave governance payload/executor contract, with no arguments decoded. This is the standard pattern for Aave V3 governance proposals, where the actual sub-actions (swaps, approvals) are encoded inside the bytecode of the payload contract that execute() delegatecalls into, rather than being visible as separate decoded actions at the proposal level. Because the calldata here does not expose the granular sub-actions, it is not possible to directly verify or refute the specific amounts, token addresses, or recipients claimed in the description against the decoded calldata. There is no evidence of a mismatch — the single execute() call is consistent with the expected mechanism for enacting this type of proposal — but the lack of decoded detail means a full independent verification of the amounts and targets cannot be performed from this data alone. Given this, I am not flagging specific discrepancies (there is no contradicting evidence), but confidence in this assessment is low since the calldata dump does not provide enough granularity to compare individual figures against the prose.
Generated by Kvorum
04Actions
- Target
- 0x9e04…9347
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 570x57ab…2922 | For | 292.7K | 50.94% | — | 1y ago |
| 2E0x2e21…f21a | For | 104.3K | 18.16% | — | 1y ago |
| EZezr3al.eth0x8659…7d0e | For | 40.6K | 7.06% | — | 1y ago |
| B90xb933…8dd1 | For | 39.6K | 6.89% | — | 1y ago |
| 870x8787…ea52 | For | 24.8K | 4.31% | — | 1y ago |
| EC0xecc2…6ac9 | For | 21.8K | 3.80% | — | 1y ago |
| 3D0x3ddc…05b0 | For | 20.1K | 3.50% | — | 1y ago |
| 8B0x8b37…2a22 | For | 10.9K | 1.90% | — | 1y ago |
| 070x0703…961b | For | 10K | 1.74% | — | 1y ago |
| 2C0x2cc1…4df1 | For | 5.2K | 0.91% | — | 1y ago |
| 080x0865…24ce | Against | 2K | 0.35% | — | 1y ago |
| 440x4444…34b3 | For | 1.4K | 0.25% | — | 1y ago |
| A50xa54f…0f31 | For | 584.8 | 0.10% | — | 1y ago |
| B30xb356…c826 | For | 480 | 0.08% | — | 1y ago |
| 7D0x7dcc…9fca | For | 22.5 | 0.00% | — | 1y ago |
| B10xb1e8…c153 | For | 8.8 | 0.00% | — | 1y ago |
| 1F0x1faf…96b1 | For | 5.1 | 0.00% | — | 1y ago |
| 2F0x2f2f…f78a | For | 2 | 0.00% | — | 1y ago |
| 050x0579…4048 | For | 1 | 0.00% | — | 1y ago |
| 010x019e…2ee3 | For | 0.3 | 0.00% | — | 1y ago |
| 6E0x6e54…aea3 | For | 0.3 | 0.00% | — | 1y ago |
| 010x0100…7cc9 | For | 0.2 | 0.00% | — | 1y ago |
| 160x168f…7400 | For | 0.1 | 0.00% | — | 1y ago |
| 790x79fa…0275 | For | 0.1 | 0.00% | — | 1y ago |
| EA0xea5b…3c36 | For | 0 | 0.00% | — | 1y ago |
07Forum
No forum thread is confidently linked to this proposal.