KVORUM
aaveSource: Aave governance v3 · #5

Aave Funding Updates (part 2)

executedJan 16, 2024, 08:19 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal (Part B of Aave DAO's funding consolidation) reallocates stablecoin holdings by depositing 1.7M USDC and 750k USDT into Aave v3 Ethereum, withdrawing all USDC from v2 Ethereum, and swapping 500k DAI and 1M USDC to GHO to support service provider payments.

Type
treasury allocation
Funding
$3.45M

Key changes

  • Deposit 1.7M USDC from Treasury into Aave v3 Ethereum(high)
  • Deposit 750k USDT from Treasury into Aave v3 Ethereum(high)
  • Withdraw all USDC (except 10 dust units) from Aave v2 Ethereum Pool(high)
  • Swap 500k DAI held in Treasury to GHO(high)
  • Swap 1M USDC (withdrawn from v2) to GHO(high)
  • Deposit remaining withdrawn USDC into Aave v3 Ethereum Pool(high)

Notable concerns

  • This is part two of a multi-part proposal and depends on completion of Part A (Polygon to Ethereum bridge transfers)
  • Significant swap of stablecoin holdings to GHO concentration
  • Requires coordination across v2 and v3 protocols on Ethereum
ContractsAave v3 EthereumAave v2 EthereumGHO token contract
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

319 words

Simple Summary

This AIP aims to consolidate Aave DAO's stablecoin holdings. It is divided into different parts that are detailed below. This is part two and it consists of depositing USDC into Aave v3 Ethereum, as well as migrating the v2 position to v3 in Ethereum. Also depositing USDT into Aave v2 Ethereum and swapping DAI and USDC for GHO.

Motivation

This AIP (Part B) when implemented ensures the Aave Protocol is sufficiently funded to support service providers receiving DAI, GHO and USDT.

The funds transferred from Polygon to Ethereum by the Aave Funding Part A AIP are to be deposited into Aave v2 and v3 as required and DAI swapped to GHO. In addition, with no USDC stream drawing from Aave v2 on Ethereum, all USDC is to be withdrawn from v2. 1.00M of this USDC is to be swapped to GHO and the remainder to be deposited into v3.

Specification

  • Deposit 1.7M units of USDC from Treasury into Aave v3 Ethereum (received from Polygon bridge)
  • Deposit 750k units of USDT from Treasury into Aave v3 Ethereum (received from Polygon bridge)
  • Withdraw all but 10 units of USDC from Aave v2 Ethereum Pool into USDC (keep 10 units of USDC as dust, as to not leave an empty reserve)
  • Deposit the balance of the withdrawn USDC, minuts the 1.0M to be swapped, into Aave v3 Ethereum Pool (withdrawn in previous step)

Swap the following asset holdings to GHO:

  • 500k units of DAI held in Treasury (received from Polygon bridge)
  • 1.0M units of USDC (withdrawn from Aave v2 Ethereum in previous step)

References

Disclaimer

TokenLogic and karpatkey receive no compensation beyond Aave protocol for the creation of this proposal. TokenLogic and karpatkey are both delegates within the Aave ecosystem.

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The decoded on-chain action set consists of a single generic execute() call to a payload contract address, which is the standard pattern used by Aave governance proposals (the Governor delegatecalls a purpose-built payload contract referenced in the 'Implementation' link). Because the calldata does not expose the internal logic of that payload contract (the specific deposit/withdraw/swap amounts and target pools), it is not possible to directly verify each individual claim in the description (1.7M USDC deposit, 750k USDT deposit, v2 withdrawal, 500k DAI swap, 1.0M USDC swap) against on-chain parameters. No contradiction is evident from what is decodable, and the single execute() call is consistent with the proposal being a multi-step payload as described. Given the opacity of the calldata for verifying specific figures, confidence is marked low and no discrepancies are flagged, since we cannot substantiate a mismatch without decompiling the payload contract's bytecode/source, which is outside the scope of the decoded actions provided. Delegates relying on this analysis should independently verify the payload contract source code linked in the References section to confirm the exact figures match the prose since this proposal type inherently hides sub-action detail behind a single execute() call.

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0fallback()chain 0x1
Target
0x1f5c…38fc
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.