#7·Delay Demo #2 Treasury Guardian

Dear Proposer,

Thank you for your proposal. Our first vote on this proposal is AYE.

The Treasurer track requires 60% quorum according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received six aye and zero nay votes from eight available members. Below is a summary of our members' comments:

Voters expressed support for delaying the treasury spend as proposed and defended the demonstration of the Treasury Guardian mechanism. Comments highlighted the enthusiasm for testing and evaluating the delay mechanism, with one remark questioning the decision against using an alternative process while still endorsing the approach. Several members noted that the experimental work was commendable and encouraged similar initiatives in the future. Testing notes provided evidence of careful examination and an exploratory mindset, and overall, the combined feedback affirmed the experimental decision to defer the treasury allocation while reinforcing confidence in the creative process behind the Treasury Guardian demonstration.

The full discussion can be found in our internal voting.

Please feel free to contact us through the links below for further discussion.

Kind regards,
Permanence DAO
Decentralized Voices Cohort V Delegate

📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate

Big fan of experiments and show cases of technology :)

Le Nexus voted AYE!

This demo is valuable, delaying spends strengthens treasury accountability.

Le Nexus invites you to join our DV Office English channel on Discord to engage in conversation about OpenGov proposals.

A technology test, there are precedents with the Parity Tipping bot and youtube tutorials even.

Disclaimer:
Our modeling includes more than 1000 non-linguistic parameters so these are only verbal observations also included in the vote calculations and they are not an extensive review of the full rationale behind this vote.

The delay demo for the treasury guardian was a success.

The goal: Delay the spend of 1 KSM scheduled to Bill on 25/3/26 (Spend #6: https://kusama.subsquare.io/treasury/spends/6) by 50 days .

The treasury guardian tool prepared a referendum to do the following:

1. Cancel original scheduled spend (Spend #6)
2. Create a new scheduled spend at 98% of original value (50 days after original scheduled spend: 14/5/26. Spend #7: https://kusama.subsquare.io/treasury/spends/7)
3. Pay out 2% of original value immediately to treasury guardian that created the delay referendum (Spend #8: https://kusama.subsquare.io/treasury/spends/8)

With the treasury guardian we now have a tool that incentivises treasury oversight. This paves the way for milestone-based scheduled payout referenda at scale.

1. Governance approves referenda that encompass several scheduled payouts based on milestones.
2. An army of treasury guardians is incentivised to keep an eye on the projects as milestones become due.
3. Treasury guardians create delay/cancel referenda with our tool and earn part of the funds they delay/cancel should their referenda be successful.

We will also be demoing how treasury spends can be canceled with our tool.