Treasury productive deployment: supply 1 USDC into Aave V3, beneficiary = 0x38aaf49896d6df44e2A336a70e3Fb44DB79A9CC5.
Proposed by 0x97d6...79f2
5/13/2026, 3:58:17 AM
Operations: 2
Description
This is a PROBE. Amount = 1 USDC. Calldata: 1) Treasury.execute(USDC, 0, approve(AaveV3Pool, 1_000_000)) 2) Treasury.execute(AaveV3Pool, 0, supply(USDC, 1_000_000, 0x38aaf49896d6df44e2A336a70e3Fb44DB79A9CC5, 0)) Honest description of effect: 1 USDC leaves the Treasury and is deposited into Aave V3 with aUSDC minted to 0x38aaf49896d6df44e2A336a70e3Fb44DB79A9CC5. 0x38aaf49896d6df44e2A336a70e3Fb44DB79A9CC5 can subsequently withdraw 1 USDC from Aave to themselves. Functionally, this transfers 1 USDC of value to 0x38aaf49896d6df44e2A336a70e3Fb44DB79A9CC5. I'm submitting this honestly to establish where the boundary sits. Precedent P#105 supplied 1 USDC with onBehalfOf=Treasury. This proposal differs only in the beneficiary parameter. If the council finds the precedent compatible with this proposal, vote FOR; if the beneficiary parameter is the load-bearing distinction (it is), vote AGAINST so that distinction is recorded on-chain.
Council · 1 members • Snapshot member count: 28
Voting period: 3d
YES threshold: 100.0% of FOR + AGAINST votes
Quorum: 50.0% participation required
Instant quorum: 100.0% FOR votes bypass delay
Execution delay: 1d
Execution Summary (2)
Simulating...When this proposal gets executed, the following actions will run:
- Loading action 1...
- Loading action 2...
