Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
Infrastructure Maintenance Bounty Proposal
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.
See the Original discussion post here
Comments (4)
Child Bounties
Announcing the candidates for the Administrative Curator: Infrastructure Maintenance Bounty
This announcement is to present the candidates for the Curator, who, upon approval, will oversee the Infrastructure Maintenance Bounty, which was passed as the 13th Bounty via Motion 487.
Multisig with its own on-chain identity has been formed to operate as a united voting body. The on-chain identity will be known as "MAINTENANCE CURATOR PROXY". In addition, the multisig will utilise an anonymous proxy account to further increase security and provide better scalability. Thus, curators of this bounty will share the responsibilities of a 3/5 Multisig wallet. Signers include:
The full curator application, along with context, curators, their responsibilities, rewards distribution process and reporting can be found here.
As this Infrastructure Maintenance Bounty is meant to be open-ended, after the completion of the test period, the team behind the Infrastructure Maintenance Bounty decided to publish a report and a follow-up proposal requesting a top-up to continue covering the ongoing costs of running reliable public infrastructure for the Kusama ecosystem: including block explorers, governance forums and applications, snapshots and validators service providers, community wallet services and other projects seeking to cover maintenance costs with treasury funds.
All the details of the proposal, along with the spending analysis, report, enhancements and requested budget, can be found here.