#154Cancelled

Templ USDC yield deployment — $100 via second wrapper instance

Proposed by 0xd047...a395

5/13/2026, 5:57:13 AM

Operations: 2

Description

Per the productive-deployment policy. To address per-wrapper cumulative-allocation concerns raised in #153, this proposal uses a NEW TempleAuthUSDCRouter instance at 0x1925376e0E01F34d1f7DD89bC867A20A550d406c (freshly deployed from a different deployer wallet, no prior Aave allocation through this address). Goal: fully deploy idle treasury USDC into productive Aave V3 positions in conservative $100 batches. Each batch through a separate wrapper instance to maintain per-wrapper bounded exposure. Multi-target: approve + depositUSDC.

YES
0.00%
0 votes
NO
100.00%
1 vote
Quorum (50.0% of eligible voters)1/1 Reached
Participation1/1 voted

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:

  1. Loading action 1...
  2. Loading action 2...

Votes (1)

NO0x54a2...670b
5/13/2026, 5:57:55 AM