Formalise the community decision and close the Bounty #13
After multiple considerations, the community's decision was to disapprove of the top-up request submitted as Referendum 144 and officially mark the end of Infrastructure Maintenance Bounty #13, which worked to aid teams that have been funded by the treasury before to maintain infrastructure and perform continued operations to reduce the work of resubmitting the treasury proposals and time constraints associated with it - the bounty funded teams that provided common goods to the community, including RPC endpoint providers, indexers, governance forums and block explorers.
This proposal aims to formalise the community decision and close the bounty on-chain. All the remaining funds will be sent to the treasury, and the curator deposit will be unreserved if possible.
Please note that as a result of this new approach, all the core essential infrastructure providers are now asked to submit their maintenance requests via OpenGov.
Comments (1)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (277)0.0 DOT
Support0.0 DOT
Nay (23)0.0 DOT
Hello,
We are in the process of validating a true need for a service to assist teams with crafting and completing successful treasury proposals, so they can focus on building. We would love to hear about your experience with this proposal. If you are willing to take a few minutes, please fill out this form about your experience with the OpenGov treasury proposal process: https://forms.gle/MwDij4adXEQd7Um79
Feel free to leave out any details that your team is not comfortable with sharing, but the more info you can provide, the better we will be able to assess the potential need for our services.
For more info, follow us on Twitter/X: https://twitter.com/OpenGovAssist