For context:

In Referendum 572 we created a 1 KSM scheduled spend (scheduled for Sept. 29th) to Bill which we wanted to first delay and then cancel with our tool: http://treasury-guardian.app/

With Ref 580 we are now demoing how our tool can be used to delay a scheduled spend (if a milestone is delayed for example). There is a video at the end of the description that shows how ref 580 was created with our tool. Here it is again: https://www.youtube.com/watch?v=tW674JeLOgw&feature=youtu.be

A full write up of the project can be found here.

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 five aye and zero nay votes from eight available members. Below is a summary of our members' comments:

The votes reflected a clear shift in sentiment after the demo was shown. One voter had previously abstained due to a delayed demo but switched after appreciating the demonstration's quality. Additional context from linked resources convinced another of the proposal’s merits, while others expressed enthusiasm about the innovative test and the potential to see the process in action. Despite some reservations about the experimental nature and doubts about further discussions with core engineers to refine on-chain spend logic, the overall response favored the proposal, endorsing the idea as a promising step forward in addressing treasury spend delays.

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 IV Delegate

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