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


Bounty Proposal: Infrastructure Maintenance 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](https://docs.google.com/document/d/1MPyabjOmkiIq4QW6UzIzJUyEzoaVOe2TgUSSQ0r2DxI/edit?usp=sharing). 

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


Infrastructure Maintenance Bounty Proposal 

Testing OpenGov Referenda during Ambassador gathering. In case approved, no funds would leave the treasury, so please feel free to either approve or reject. 

![](https://i.ytimg.com/vi/ptVo5YfmY6k/maxresdefault.jpg)

Testing Referenda 

![](https://i.postimg.cc/qMNspcGj/Screenshot-2022-10-04-at-16-17-45.png)
As **Infrastructure Maintenance Bounty** was 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](https://docs.google.com/document/d/1tCmnNhXmqNbBQtUEbuIyvwXT99uVFkUZ45GdWRNa2uQ/edit?usp=sharing) 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](https://docs.google.com/document/d/1tCmnNhXmqNbBQtUEbuIyvwXT99uVFkUZ45GdWRNa2uQ/edit?usp=sharing).

_*Please note that you will not be able to see the beneficiary identity on-chain (this is the address of the bounty, created once the bounty proposal is accepted), but you will be able to check this on [Subscan](https://kusama.subscan.io/account/F3opxRbN5ZbjJNU513biNdUuzGvk6gSBmwggQXh7rttXx6k)_ 

Infrastructure Maintenance Bounty Top-up

force_batch

dispatch_whitelisted_call_with_preimage

As five more parachains have requested an HRMP channel opening with Statemine, this Referendum aims to accept and open return channels - the following `batch` call aim to be executed on this proposal for each of the parachains:

1. A `forcetransfer` of 10 KSM from the Treasury to Statemine sovereign account.
2. A `forceopenhrmpchannel` from Statemine (1,000) to \[ParaID\].
3. A `forceopenhrmpchannel` from \[ParaID\] to Statemine (1,000).

ParaIDs for each parachains requesting the channels and proposals requesting this by the parachain teams:

- Amplitude: 2,124
- MangataX: 2,110
- Imbue: 2,121
- Tinkernet: 2,125
- GM Parachain: 2,123

The encoded call can be found [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x18041418020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300004c080000e8030000009001003c074c080000e8030000e80300000090010018020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300003e080000e8030000009001003c073e080000e8030000e80300000090010018020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e803000049080000e8030000009001003c0749080000e8030000e80300000090010018020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300004d080000e8030000009001003c074d080000e8030000e80300000090010018020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300004b080000e8030000009001003c074b080000e8030000e803000000900100).

A New Batch Of HRMP Channels: Amplitude, MangataX, Imbue, Tinkernet, GM Parachain

The proposal aims to resubmit [Referendum 243](https://kusama.polkassembly.io/referendum/243) (already approved), this time using OpenGov in order to extend the lease of Encointer's Common Good Chain by eight lease periods. The last proposal failed to enact due to some changes in logic and scheduler that restricted the call. Hence this proposal aims to put forward the extension request once again.

Contextual information by Encointer can be found below:

### Encointer's common good lease run out on Dec 12th 2022.

Based on the following progress reports, we ask the community to appreciate our work done so far and grant us another 48 weeks.

- [Our recent treasury proposal](https://docs.google.com/document/u/2/d/1eTyZGCTCzo7ZGonVtAmJmc5QYYI0qYHab6z8w56B_F0/edit) includes a detailed report on what we have achieved until June 2022 and what our plans are for the future.
- Our [delivery report](https://kusama.polkassembly.io/motion/510#3f6f0d94-639f-49ec-a0ee-1f4ace1a37c8) on above treasury grant updates the information with achievements in the June-Sept 2022 period

We think Encointer has achieved a lot and is gaining momentum, both with its [pioneer community in Zurich](https://leu.zuerich/), but also with [newly launching communities worldwide.](https://trello.com/b/1Yhln6NT/encointer-community-leader-applications)

Our original argumentation for the common good is still valid and can be found [here](https://kusama.polkassembly.io/post/610). What we'd like to add to our value proposition of pure sybil resistance is our approach for [inclusivity](https://polkadot.network/blog/introducing-encointer-making-web3-truly-inclusive/) which has resonated well in the community.

The initial passed referendum to register Encointer as common good is [here](https://kusama.polkassembly.io/referendum/158).

While the Encointer team is aiming to diversify its funding sources, support by the Kusama treasury will be necessary for the upcoming period to continue working at the current pace. Therefore, we will submit our next treasury proposal soon.

Preimage hash: `0x3249b18124aab52cd632f6759c7e46e10bac60b6f3411247e92b44babc67fd41`

Extending Encointer's common good lease by 48 weeks

As we navigate OpenGov, we discovered that [Referendum 1](https://kusama.polkassembly.io/referenda/1) and [Referendum 2](https://kusama.polkassembly.io/referenda/2)  wouldn't enact successfully because the call we used (treasury.ApproveProposal) will only be enacted successfully with root origin. Consequently, the teams have resubmitted their proposals:

- on the `Treasurer` and `Big spender` track (same one)
- with the call `treasury.Spend` (including the amount in KSM for the allocation)

As a result, the new submissions can be found using the following links:

- [Referendum 3](https://kusama.polkassembly.io/referenda/3) aiming to fund the development of **Snowbrdige**
- [Referendum 5](https://kusama.polkassembly.io/referenda/5) seeking to finance **Polkawatch's** decentralization analytics Parachain support and continued operations

This particular submission service utilises the Referenda Canceller track and tries to cancel referendums 1 and 2 (replaced by 5 and 6).


Referendum aiming to cancel two invalid Referendums (1 & 2)

Using a `batch` call, this Referendum aims to cancel proposals that have been approved by the community but have failed to enact on time due to UI misconfiguration.

Namely, as we started to navigate OpenGov, it was brought to our attention that a misinterpretation of the parameter `after`, which is NOT an absolute block number but a delay expressed in blocks, implied that after approval, these referenda would take years to enact.

Among others, Referenda: [4](https://kusama.subsquare.io/referenda/referendum/4), [5](https://kusama.subsquare.io/referenda/referendum/5), [6](https://kusama.subsquare.io/referenda/referendum/6), [7](https://kusama.subsquare.io/referenda/referendum/7), [9](https://kusama.subsquare.io/referenda/referendum/9), [10](https://kusama.subsquare.io/referenda/referendum/10), [11](https://kusama.subsquare.io/referenda/referendum/11), currently sitting in the scheduler, are expected to be approved from 1025-1100 days from now.

However, as the teams have already resubmitted their proposals with the updated parameters (see [referenda history](https://kusama.subsquare.io/referenda) of various tracks), I am bringing forward the following call to cancel the proposals and avoid any complications in the future.

![](https://i.postimg.cc/zGG0cDTX/Screenshot-2023-02-06-at-14-43-33.png)

Cancellation of the proposals that are wrongly scheduled

Kusama auctions are scheduled using the Scheduler Pallet and its recurring feature. This pallet offers two options: the frequency of execution (in blocks) and the number of times it should be executed. Unfortunately, as the scheduled auctions queued on Scheduler by [Referendum 72](https://kusama.subsquare.io/referenda/referendum/72) and [Referendum 81](https://kusama.subsquare.io/referenda/referendum/81) have been misconfigured and subsequently cancelled, it has become necessary to propose this Referendum with the right parameters to ensure that all auctions are properly scheduled throughout the year and the Kusama community can continue including new parachains and allowing those already up and running to renew their slots in 2023.

Please note that from the original schedule, originally approved by the community, two auctions have been submitted via the Auction admin track

- [ https://kusama.polkassembly.io/referenda/91](https://kusama.polkassembly.io/referenda/91)
- [https://kusama.polkassembly.io/referenda/96](https://kusama.polkassembly.io/referenda/96)

And a third one will also be submitted via the same track. After this one, if approved, the 2023 schedule will continue as stated [here](https://docs.google.com/spreadsheets/d/1KyNq6IGrzrfx0ZiMuRY0gMZSqv6la1fNjWF3rOD1zkU/edit?usp=sharing).

The preimage submission can be seen [here](https://kusama.subscan.io/extrinsic/16647098-2).

The image can be found [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x1804201d0281edbd9bec51fc9d78be1dc45e65c7c97ff25d8fb0df5e190e559181831249fb4c6e010101508b010004000000004800e2a50100701d022e1895be3594bbbd39f330a843f221425b680653652b26fc1320533d8eecbf7b00ac0701018051010007000000004800f1d2741d023f695d577cd80ceab19696358d0965bd903a4a4622380a564dc6b9783b756a0e80e61001018051010007000000004800f1d2781d02f8a869528ddc7c0d40aeceda15497713ebb931c931424043f9a4df89af4a1ac900211a01018051010007000000004800f1d27c1d020b80ba0c51368b431d999fc5bab0cea73c5f8cb2520e4eb41c7c309b68d2cdf5805b2301018051010007000000004800f1d2801d02630ed60985a63f89b71e168f8cbcec645b27e37f1840f4e81d96c7fa248e63ee00962c01018051010007000000004800f1d2841d027e65636788051a7e026b57a4fa11c8854e181e5dcfd688dbe25bb449b0555c2680d03501018051010007000000004800f1d2881d022e7dae2f2fd127478f7d20a0da689b7f8abbb0b5f2f2a65ed18d31c9815f8404000b3f01018051010007000000004800f1d28c)

Please make sure to review and cast your votes!

Kusama Auctions for 2023

![](https://i.postimg.cc/yx1LT7nJ/Screenshot-2023-03-21-at-12-06-06.png)
After delivering a report showcasing the child bounties approved at the community request, we aim to request a top-up of the [Infrastructure maintenance bounty](https://kusama.polkassembly.io/bounty/13), which works to aid teams that have been funded by the treasury before for the development of their ideas, to maintain infrastructure and perform continued operations to reduce the work or to resubmit 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. The bounty has been running for roughly a year now and has helped fund multiple infrastructure proposals, whose details can be found in the spreadsheet here. 

This follow-up top-up will enable us to continue with our efforts as well. 

Details of this proposal, including what we have achieved so far, our future goals, and an estimated breakdown of the requested top-up, can be found in the [proposal document](https://docs.google.com/document/d/1x-KWa7U0oqFuXh_adA5e5BNYqz3ILCdqoDCGE2A5FuY/edit?usp=sharing).

Infrastructure Maintenance Bounty Top-up request 

In line with Polkadot's approach, proposing the closure of Bounties [n.16](https://kusama.subsquare.io/treasury/bounties/16) and [n.21](https://kusama.subsquare.io/treasury/bounties/21). Both bounties are completed, and the curator has been removed due to an expired expiration date without extension.

Please note that the action of closing the previously funded bounty would return any remnant funds on the bounty account to the treasury.

Bounty Closure Proposal: n.16 and n.21

After multiple considerations, the community's decision was to disapprove of the top-up request submitted as [Referendum 144 ](https://kusama.polkassembly.io/referenda/144) and officially mark the end of **[Infrastructure Maintenance Bounty #13](https://kusama.polkassembly.io/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](https://scribehow.com/shared/Submitting_a_Referendum_to_the_Kusama_Network__BZxcgSYkRCaCVvm5Sxjp9g).*