New scheduled payout to test treasury guardian
Unfortunately the batch call in #580 did not execute successfully.
Issue: Our tool wrongly set the validFrom field to "0" instead of "None" for the immediate transaction to the treasury guardian. (2nd transaction in the batch call of #580).
We will be updating our code and trying the delay again.
The current scheduled spend (ID 5) to Bill created in #572 expires in 15 days. Unfortunately that is not enough time for a new treasurer proposal to delay it since the voting period on the treasurer is 14 days + 2 days confirmation + 1 day execution.
This proposal creates another scheduled payout (way further in the future this time) that we can delay with our treasury guardian tool to demo its usage.
Comments (8)
Requested

Proposal Passed
Summary
0%
Aye
0%
Nay
Aye (17)0.0 DOT
Support0.0 DOT
Nay (3)0.0 DOT
🏛️ REEEEEEEEEE DAO
REEEEEEEEEE DAO is a decentralized collective body committed to serve Polkadot Opengov. Our mission is to provide high-quality assessments on referenda to ensure outcomes that strengthen the Polkadot ecosystem. Each referendum is reviewed carefully by our DAO members through the scope of technical, strategic, and governance.
📋 Community Feedback
💬 Open Communication Channel
For further discussion and detailed feedback, please reply to this comment.
This feedback represents the collective voice of REEEEEEEEEE DAO members participating in Polkadot governance.
Thank you for prompt voting. Much appreciated.