OnlyDefiGuy had the courage to face the dragon of #684 on behalf of Dotizens, sharing his expert report on #684 here in this doc.

Regardless of whether we voted AYE on NAY, we should value this kind of courage and expertise. It clearly requires skin as thick as a dragon when proposals are this contentious and complex.

This "Big Tipper" tip [up to 999 DOT] attempts to Create a Multistage Payout Proposal with 3 treasury.spends:

1. at block 21,000,000, pay 150 DOT (est. May 30)
2. at block 21,403,200, pay 300 DOT (est. Jun 27)
3. at block 21,806,400, pay 599 DOT (est. Jul 25)

This tip of up to 999 DOT depends on #741 - Move Part of Treasury to Asset Hub passing. [The track determination logic is being tested between #780 and #781 (150+300+599 = 1049 > 1000 vs 250), lets see what happens]

Importantly, this multistage payout mechanism could be used by Big/Medium/Small proposers for meeting time-based and/or delivery-based milestones. It can almost certainly can be used for USDC+USDT payments as well, which factored into the 1MM DOT vs 10MM USD costs of #684 itself.

Assuming this passes (and the staged payout mechanics works in Polkadot), we imagine someone could submit a treasury.voidSpend on the 3rd payment. This is not because we believe OnlyDefiGuy doesn't deserve 599 DOT (we do, because dragon fighting is hard work), but because it is clear the community learning this "voiding skill" can be explored to significant effect.

Or maybe OnlyDefiGuy will fight off some more dragons by then =)

Note:

• #780 is in DOT but exceeds the 250 DOT Small Tipper track limit (150+300+599 = 1049 > 250 DOT)
• #781 is in DOT but exceeds the 1000 DOT Big Tipper track limit (150+300+599 = 1049 > 1000 DOT)
• #782 is in USD but should not exceed the 1000 DOT Big Tipper track limit (1000+2000+3000=6000 USD < 1000 DOT [but is based on the AssetConversion pool])