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.
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.