Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
Canceled; New Proposal considering feedback: #1776 (De-Risking the Treasury)
This Referendum is canceled. Please (continue to) vote Nay.
A new version incorporating the feedback received here is up for vote: New Proposal
Voters have become increasingly cautious, making it harder for projects to gain approval for their proposals. Our project introduces a clawback mechanism to significantly reduce risks to the Polkadot Treasury. By implementing this safeguard, we aim to lower financial exposure and provide voters with peace of mind to confidently approve funding for impactful projects.
With our tool, a group of decentralized treasury guardians is incentivized to oversee scheduled payouts and intervene when necessary to protect the Treasury.
Key features of our proposal:
- No upfront payments are requested.
- All payouts are tied to milestone delivery, with sufficient time for the community to review and delay/ cancel disbursements if needed to ensure accountability on our behalf.Milestone Delivery Deadlines:
Milestone 1: Nov 9 2025 -> Scheduled Payout: Dec 29 2025
Milestone 2: Dec 7 2025 -> Scheduled Payout: Jan 26 2026
Milestone 3: Jan 4 2026 -> Scheduled Payout: Feb 23 2026
Milestone 4: Feb 1 2026 -> Scheduled Payout: Mar 23 2026
Milestone 5: Mar 1 2026 -> Scheduled Payout: Apr 20 2026
Milestone 6: May 29 2026 -> Scheduled Payout: May 18 2026
We are passionate about leading the charge to de-risk the Treasury, enhance its efficiency, and better align the interests of token holders and proposers. We eagerly look forward to collaborating with the Polkadot community and new + existing ecosystem teams to achieve these goals.
Read our full proposal here.
Comments (13)
Quick Q:
In the full proposal doc:
Project Lead: An experienced Polkadot builder with prior contributions to the ecosystem.
-> There is an hyperlink to github, is it supposed to be linked to a specific github?
The current hyperlink is:
https://github.com/?tab=repositories
Not very useful here ;)
So who's the project Lead ?
@SuperDupont-Nexus Oopsies. Fixed! Thanks for pointing it out.
Thanks for the proposal, glad to see that your tests on Kusama worked out and I am very aligned with the need for accountability and follow up on treasury spends. I appreciate that you have already come with an MVP and a video demo, showing you want to be exemplary, also seen by showing example of what can be done with this tool by presenting your own proposal with clear milestones defined and explained.
I do have a few questions:
@🌎 ValidAndina 🏔️ Thank you for your comment and questions.
1. The treasury guardian app is just a UI on top of OpenGov. It is a dashboard to track upcoming scheduled spends and help users prepare delay/cancel referenda. So naturally it inherits the permissionless nature of OpenGov. Anyone can create a delay/cancel referendum with our tool -> anyone can be a treasury guardian. Everyone is incentivised to become a treasury guardian since treasury guardians earn part of the funds they protect should their intervention be successful.
We have ideas to bootstrap initial interest in treasury guardianship and showcase the earning opportunities. If we fall short on this milestone (just like any other milestone) anyone can use our tool to cancel/delay payouts to us.
2. Anyone can place the decision deposits on delay/cancel referenda: you, me the guardian themselves or anyone else that wants to see a referenda get to the voting stage. The guardian would have to pay the preimage deposit though: approx. 41 DOT (refundable).
3. Delay/cancel referenda have to go on the treasurer track since the other tracks don't have the required permissions. OpenGov has built in deterrents to abuse/spam. These also get inherited by our project naturally.