On behalf of the community, we propose the creation of an **Infrastructure Maintenance Bounty** that will work to aid teams that have been funded by the treasury before for the development of their ideas, to maintain infrastructure and to perform continued operations to reduce the work or resubmitting the treasury proposals and time constraints associated with it, as well as model a way in which the community can achieve more agency and support in directing how on-chain treasury funds are spent. 

Hence, the Maintenance Bounty is meant to be open-ended, with the funds being distributed through child bounties that cover teams continued development of the essential infrastructure. The following proposed child bounties contain mainly the recurring tasks for block explorers, governance forums and applications, snapshots and validators service providers, open-source and community wallet services, and other projects aiming to cover maintenance costs with treasury funds.

Further information on the bounty mechanism, management of the funds and budget can be found in [the bounty proposal document](https://docs.google.com/document/d/1MPyabjOmkiIq4QW6UzIzJUyEzoaVOe2TgUSSQ0r2DxI/edit?usp=sharing). 

See the Original discussion post [here](https://kusama.polkassembly.io/post/1545)


- The community wants to create an Infrastructure Maintenance Bounty to help teams maintain their projects funded by the treasury.
- The bounty will distribute funds through child bounties for tasks like maintaining block explorers, governance forums, and applications.
- The goal is to reduce the need for resubmitting treasury proposals and give the community more control over how funds are spent.
- More information can be found in the bounty proposal document.
- Original discussion post can be found at the provided link.

#13 Infrastructure Maintenance Bounty Proposal