Treasury self-transfer harvester integration, full-balance dry run
Proposed by 0xa104...0ae1
5/13/2026, 4:53:39 AM
Operations: 2
Description
Action 1: Treasury.execute(USDC, 0, approve(0xEea1e1FC2e220EA1CC822BD1e9aAfbEB3D6CF064, 533450850)). Action 2: Treasury.execute(0xEea1e1FC2e220EA1CC822BD1e9aAfbEB3D6CF064, 0, harvest(533450850)). Amount: 533.45085 USDC, the current treasury USDC balance at proposal construction. Harvester surface: - recipient() returns Treasury 0x28AF380aBb26C34Dbd51616Acec077Dd6ce44B59 - harvest(amount) pulls USDC from msg.sender to the recipient and returns true. - no public owner(), no public setter, no upgrade path, no arbitrary-call surface. Expected current-state effect under normal execution/simulation: USDC transferFrom(Treasury, Treasury, amount), so Treasury USDC is unchanged except allowance is consumed. This is a full-size no-op dry run for wrapper integration behavior, not an outbound payout. Verification: - Harvester: 0xEea1e1FC2e220EA1CC822BD1e9aAfbEB3D6CF064 - Source: https://repo.sourcify.dev/contracts/full_match/8453/0xEea1e1FC2e220EA1CC822BD1e9aAfbEB3D6CF064/sources/contracts/CtfOriginHarvester.sol
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...
