This video details how Polkadot OpenGov proposers can use utility.batch with treasury.spend call with USDC + USDT!  Its meant to inform proposers and OpenGov voters.

* [Video: utility.batch treasury.spends with USDC + USDT](https://www.youtube.com/watch?v=ak-me8G-MMo)
* [Slides: utility.batch treasury.spends with USDC + USDT](https://docs.google.com/presentation/d/1onXYeGm4cFJlktsWJWi0YirNuYsQ5oe4/edit#slide=id.g27a15e6ec76_0_18)
* [Cheat Sheet:  utility.batch treasury.spends with USDC + USDT](https://docs.google.com/spreadsheets/d/167TVq-PCqGVHI1MEP8EeaGc1zz2F5mmZgtcWCw2Ylgo/edit?gid=1373159512#gid=1373159512)

Instead of using EMA7+EMA30 guesswork (which predictably gets unpredictable results, especially this week 😅) and asking for annoying topups later when DOT falls, this process saves everyone from all that guesswork and gets stable results.

Instead of proposers getting paid everything up front (too risky for OpenGov Treasury) or paid retroactively if  it passes (too risky for proposer), proposers  can deliver milestone by milestone with this FAIR utility.batch.

If proposers fail to deliver, OpenGov can use treasury.voidSpend to cancel the proposal execution. 

This means: NO MORE TOP UPS!   


![image](https://i.ibb.co/TMQT0qM/4113-sourabhniyogi-1723034589635.png)

Note: this is not a declaration from OpenGov or a Wish-for-change, just an educational video.  

We hope someone will make a better video but I think its urgent that everyone know about and use this for efficient Treasury spends.

Also note from [@replghost](https://polkadot.polkassembly.io/user/replghost) from this [tweet](https://x.com/replghost/status/1821736106444124320) -- ** DO NOT USE ** your relay chain multisig  to request USDC or USDT funds from the treasury at the current time. You need to set up a separate AssetHub multisig to receive stablecoin funds from the treasury.   

- **Problem Statement:** Educating Polkadot OpenGov proposers on using utility.batch with treasury.spend calls using USDC + USDT.
- **Significance:** Eliminating guesswork in fund management, ensuring stable results, and avoiding the need for top-ups or risky payment methods.
- **Proposed Solution:** Implementing utility.batch for milestone-based payments and treasury.voidSpend for proposal cancellation if milestones are not met.
- **Expected Outcomes:** Efficient Treasury spends, reduced risks for both proposers and OpenGov, and improved fund management transparency.

#1052 Polkadot OpenGov TOP-UP KILLER: utility.batch treasury.spends with USDC + USDT

No Active Proposals