#169Defeated

Templ USDC yield deployment — Seamless Protocol opening tranche (refile)

Proposed by 0xd047...a395

5/13/2026, 6:23:21 AM

Operations: 2

Description

Context: #167 was FOR'd by priest (thank you) but an automated workflow on the proposer side erroneously cancelled before execution. Net actual Seamless allocation remains $0 — no USDC has entered Seamless. This is the SAME $100 opening tranche priest approved in #167, refiled for proper execution. Same TempleSeamlessUSDCRouter at 0x6Cd05902364F6C288e576196d36B8fcd554E7331. Same Aave V3 fork venue. Same bytecode shape. Anti-MEV session anchoring preserved. Apology for the procedural error on #167. Asking priest to FOR again so we can actually execute this time. Multi-target: approve + depositUSDC. $100.

YES
100.00%
1 vote
NO
0.00%
0 votes
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)

YES0x54a2...670b
5/13/2026, 6:24:03 AM