candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Dear Kusama community,
Collators on System Parachains are provided with minimal rewards for block production and small incentives in terms of transaction fees. This reduces incentives for Collators to act in a favorable manner and they may also be inclined to under-resourcing their hosts to save costs. Collators should receive funding for the provision of their services. Ultimately, this should be provided by the chain in a preferably sustainable manner. Implementation of such a system is a long-term solution. In the medium term, funding for collators can be provided by the respective Treasuries in the form of a bounty. This allows funding to be pre-allocated and independently managed.
This proposal is the final monthly operating costs payment for service providers in Q4 2023. Future cost compensation will be done under the <a href="../post/2613">Kusama System Parachain Collators Bounty 20</a> starting from January 2024.
<a href="https://docs.google.com/document/d/1UQi_DFP99i-VE8tOEQQHR10xqbIPHLqGHNW0f1imuEE/edit?usp=sharing">Full Proposal</a>
The proposal aims to secure 844.654 KSM for Collators on the Kusama System Parachains network for services delivered for 3 months - 10-12/2023.
<img src="https://example.com/your-image.png" alt="" /><img src="https://i.ibb.co/W5Jdk2r/Screenshot-2023-11-21-at-23-52-39.png" alt="" width="640" height="629" />
We encourage the Kusama community to review this proposal and provide any feedback or suggestions.
Thank you!

- Collators on System Parachains need to be rewarded for their services.
- Collators may be inclined to under-resource their hosts to save costs without proper incentives.
- Funding for collators can be provided by the respective Treasuries in the form of a bounty.
- This proposal aims to secure 844.654 KSM for Collators on the Kusama System Parachains network for services delivered for 3 months - 10-12/2023.
- The Kusama community is encouraged to review the proposal and provide feedback or suggestions.

Confirming

medium_spender

Kusama System Parachain Collators - Tips Q4/2023

Deciding

small_spender

 Reimbursement proposal after a seed phrase has been lost"

Stakeworld maintains a few services which are connected to it's rpc services. For example we keep a [database size overview](https://stakeworld.io/docs/dbsize) which gets its size information from the archive rpc nodes. 

The last treasury requests for rpc services did not get through so we plan to scale down/stop these services, which would also mean we have to stop with the database size overview service. We would like to continue this service but will need some funding for this.

Also we revived our [snapshot](https://stakeworld.io/docs/snapshot) service. The service was still online but was not being updated anymore. 

Since it was getting used more and more again in light of the recent beefy introduction which disables warp sync and the update notes referal to our snapshot service as a solution (for the time being) we refreshed our snapshots to a more current state and after discussions on element are also considering including rocksdb again. This will probably be only for a few months untill warp sync gets re-enabled with beefy. 

See [here](https://github.com/stakeworld/stakeworld-treasury/blob/master/2023-Q4.kusama.md) for the proposal.

Regards,
Max | Stakeworld.io

![](https://raw.githubusercontent.com/stakeworld/stakeworld-treasury/master/2023-Q4-dbsize.png)
![](https://raw.githubusercontent.com/stakeworld/stakeworld-treasury/master/2023-Q4-dbsize2.png)

Database size service and temporary snapshot service revival

This is a follow up proposal to what we submitted before:

> [#229 Subscan | Infrastructure Costs of Subscan for Kusama & Statemine (from July to December 2022)](https://kusama.polkassembly.io/referenda/229)

Subscan is an essential block explorer and analytics tool for the Substrate ecosystem, providing valuable insights to the Substrate community. However, the maintenance and operation of Subscan requires a significant investment of resources, including server infrastructure, security, and personnel costs. Therefore, we propose reimbursing the operation and maintenance fee for Subscan for the period **January to September 2023** from the Kusama treasury to ensure its continuous operation and maintenance.

We highly value feedback from our community users, and over the past few months, we've made substantial efforts to reduce infrastructure costs. The results have been both effective and gratifying. Starting from July 2023, the operational expenses have gradually decreased and have recently stabilized. As an illustration, taking our GCP bill as an example, the costs for the past week have decreased by more than 50.52% compared to their historical peak. 
For specific parameters and billing details, please refer to the "GCP Bill" section below.
For our specific development efforts, please refer to the "Operations and Maintenance Cost Reduction Plan" section below.

The growth of Subscan is intrinsically tied to the support of our community, which we deeply appreciate. We aspire to enhance community involvement in Subscan's decision-making processes. As a result, we propose a gradual shift in Subscan's development approach, starting from November 2023, towards a community-developer collaborative model. In this new framework, Subscan's development will be guided by the needs and feedback of the community. Features with the highest demand from the community will be prioritized for development, aligning more closely with the ecosystem's requirements. While we have implemented some of these principles in the past, we recognize that they have not been as open and transparent as desired. Our aim is to continually improve upon this aspect. And the specific plan will be officially announced in December!

Please view the detailed proposal [here](https://docs.google.com/document/d/1MJOhO645uJm5y5Axok_NJCGLxMK8ZiESw_qw7Ff2ldA/edit).

Subscan is a tool that helps people understand Substrate. It needs a lot of resources to work, like servers and people to keep it running. They want to use money from the Kusama treasury to pay for it from January to September 2023. They have been working hard to make it cost less, and it has been working. They want to work more with the community to make Subscan better, and they will announce a plan in December. You can read more about it in the proposal.

big_spender

Subscan | Infrastructure Costs of Subscan for Kusama & Statemine Networks (from January to September 2023)

We're writing to inform you about the decision to deregister Parachain ID 2118 from the Kusama network. Para ID 2118 is currently locked, we've decided to deregister it from the Kusama network.

Preparing

root

Deregister 2118

small_tipper

Please vote nay

Please ignore

Vote Nay

big_tipper

This referendum updates the Kusama Relay Chain and its Asset Hub and Bridge Hub to v1,000,000, with runtimes pulled from the [Fellowship v1.0.0 release](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.0.0). See the release notes for information specific to this release.

Requires whitelist by https://kusama.subsquare.io/fellowship/referenda/51

Approved

whitelisted_caller

[Whitelisted Caller] Referendum #297: Upgrade Kusama v1,000,000

Dear Kusama community,

This proposal is a continuation of [two previous milestone proposals ](https://kusama.polkassembly.io/post/2431)aimed at improving the Kusama OpenGov. The first proposal, Milestone 0, addressed OpenGov issues by developing a proposal and audit templates, initiating community discussions, and creating audit reports. The second proposal, Milestone 0.5, expanded the initial project by introducing the program to onboard additional proposal Auditors to enhance the decentralization and accuracy of score results.

In the previous period, we successfully completed a total of 54 audits, of which 19 were conducted by auditor candidates. One of the candidates, [Abdulbee](https://kusama.polkassembly.io/referenda/165) successfully completed the full auditor onboarding process being approved by Kusama community via an on-chain OpenGov tip.

**Problem**

An additional challenge in the current proposal evaluation process is the lack of constructive feedback during the discussion phase. To address this, appointed auditors will shift their focus by becoming more involved in the earlier phases of proposal development. This proactive approach will help proposers receive feedback and address potential weaknesses in their proposals before they are submitted onchain, giving them time to evaluate the feedback and make improvements.

**Proposal**

In **Milestone 1**, the primary objective is to continue onchain proposal audits, further expand Auditor tasks, continue collaboration with Polkassembly and introduce Auditor and Reviewer roles.

To ensure transparency and community involvement, our main goal is to transfer the Audit process to the Kusama community. This will be achieved by moving the Audit report work to the **post-paid OpenGov Tips,** where approved auditors will be compensated for their efforts. This approach ensures fairness and accountability in the process while keeping it open to the community.

In this proposal, we present the continuation of the Audit team work, with the aim to deliver Audit Reports for 60 treasury proposals over a period of 2 months. Our goal is to ensure that these proposals receive the evaluation and feedback they deserve. All work will be post-paid through self-submitted tips, with auditors initiating self-tips for their completed proposal audits. To avoid overloading the treasury track, a tip must cover compensation for a minimum of 5 audit reports.

To effectively evaluate project proposals using the Audit Template, it is essential to have an objective and standardized grading system in place. The following grading criteria are taken into consideration by the audit team when creating audit reports on proposals

![](https://i.ibb.co/PmkpVMD/Screenshot-2023-04-20-at-11-05-51.png)

**Milestone 1.5** is a continuation of [Referenda #67 - Proposal Extension](https://docs.google.com/document/d/1RcWEpT5C1u4dNUH4EWCaJfpQ4qOGV19AMXPwj8qSWeY/edit#heading=h.e126djyh5msy) with the goal to continue education and onboarding of additional community auditors. 

All details can be found in the [Full proposal.](https://drive.google.com/file/d/12dT6RWkiChINTADRnQQuYHLZK_coDPdq/view?usp=sharing)

Proposal [Discussion topic](https://kusama.polkassembly.io/post/2562)


Thank you!

- The Kusama community is working on improving the Kusama OpenGov.
- They have completed 54 audits, and one person has been approved as an auditor.
- They want to give feedback to proposers earlier in the process to help them improve their proposals.
- They want to transfer the Audit process to the Kusama community to ensure transparency and fairness.
- They will continue to audit proposals and introduce new roles in Milestone 1 and 1.5.

OpenCommunity Governance - Proposal Audit Reports

The substrate-api-client is a Rust-library for connecting to a substrate-based node via RPC. It is an alternative to subxt, which provides a similar functionality. RPC clients are needed in any software component, connecting to a substrate parachain. Therefore it is advisable, that there is more than one client available for Rust developers. Apart from that, the substrate-api-client fills a gap, providing the possibility to create extrinsics in a no_std-environment. Thereby facilitating extrinsic creation from within trusted hardware (like Intel sgx). This has a big potential for further usage in IoT environments. Last but not least, the substrate-api-client has an easy-to-use interface and comes with many practical examples, which makes it a good option for new developers.

This proposal aims to fund:

1. maintenance and support for the substrate api client over 3 months (Nov-22 until Jan-23).

2. evaluation and design of two new features:
     - CLI-wallet implementation
     - full no_std-compatibility

See the [discussion](https://kusama.polkassembly.io/post/1923) and our [full proposal](https://docs.google.com/document/d/1miIIMyHsNzdoZejVdBiV_u3NLyj7CHsr9uWBdKonrtQ/edit?usp=sharing) for the details.

Substrate-api-client is a Rust-library that helps connect to a substrate-based node via RPC.

It is an alternative to subxt, which provides similar functionality.

It fills a gap by allowing the creation of extrinsics in a no_std-environment, which is useful for trusted hardware like Intel sgx.

It has an easy-to-use interface and comes with many practical examples, making it a good option for new developers.

The proposal aims to fund maintenance and support for the substrate api client over 3 months and the evaluation and design of two new features: CLI-wallet implementation and full no_std-compatibility.

Treasury Proposal: Maintenance for the substrate-api-client Nov-22 to Jan-23

Hello everyone!

 With this post, we are requesting a top-up to the Moderation Team Bounty to continue funding their contributions and support to our community.

 Due to the current market conditions, we are requesting this top-up earlier than we expected.

 In addition, somes changes have been made to the initial proposal.

 All of these changes and the details of the proposal, along with spending analysis, can be found [HERE](https://docs.google.com/document/d/1aFniLjcaNHc4ehJyIy0zQbWJJsEHqWuCRxX0szggPxk)

 Original Bounty Top-up Post can be found [HERE](https://kusama.polkassembly.io/bounty/14#a22a560c-fc0d-4d3c-8ff3-5890e08b79af) 

 Thank you for your attention!

- The post is requesting more money to support the Moderation Team Bounty.
- The request is being made earlier than expected because of current market conditions.
- Changes have been made to the original proposal.
- More details about the proposal and spending analysis can be found in a Google document.
- The original post about the Bounty Top-up can be found on a website called Polkassembly.

treasurer

Treasury Proposal: Moderation Team Bounty Top-up

Math Crypto, has put together a batch delegation [steps guide](https://www.math-crypto.com/opengov/batch-delegate/ ) and [web page](https://backend-opengov.math-crypto.com/) with a delegation hash generator for OpenGov / Gov2 on Kusama.

This is helpful to anyone that wants to delegate the votes of all gov2 tracks to a single account in a single transaction.


---


From my side as the proponent of this Referenda (apart from tipping a fellow 1KV member for the work done) I also wanted to open a Tip under the new gov2 in a track that hasn't been used before and see it unfold, nonetheless gov2 is here and ready to be used!

- Math Crypto has made a guide and website to help people delegate votes for OpenGov/Gov2 on Kusama.
- This helps people delegate all their votes to one account in one go.
- The person who made this guide also wants to give a tip to someone and try out the new gov2 track.
- Gov2 is now available for people to use.
- This will make it easier for people to participate in voting on Kusama.

Gov2 - Batch delegation step guide

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


- OpenGov discovered that Referendum 1 and 2 wouldn't work because of a problem with the call they used.
- The teams have resubmitted their proposals on the Treasurer and Big spender track with a different call.
- The new submissions are Referendum 3 for funding Snowbrdige development and Referendum 5 for financing Polkawatch's decentralization analytics Parachain support and operations.
- There is also a submission to cancel Referendum 1 and 2.
- The new proposals can be found using the links provided.

referendum_canceller

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


[Original treasury submission, that wont pass due to not applicable root call  (treasury.ApproveProposal) can be found [here](https://kusama.subsquare.io/referenda/referendum/2)] 

Hi Community,

We recently launched [Polkawatch decentralization analytics on Kusama](https://twitter.com/polkawatch/status/1578348493303083008), and [Nomination Pools](https://twitter.com/polkawatch/status/1583591038572036098) support.

The community is becoming more and more aware of the need for effective decentralization in our Ecosystem.

The interest peaked with a recent[ deplatforming event of Solana nodes](https://twitter.com/polkawatch/status/1588130270917627910) by a Network operator. 

We are been contacted by other teams of our community: Wallets, Parachains, Data Scientists, etc That want access to the data and help contribute to bringing awareness to the ecosystem. Which I think is good news.

Parachains are secured by the rely chain, but they are still vulnerable to censorship. Censorship could come from dishonest collators, deplatforming from network operators or sudden regulatory changes from hosting Countries. Despite been secured by the rely chain, parachains would benefit from decentralization analytics too.

On this proposal we aim to bring parachain support for Polkawatch, on top of continued operation of the service and other minor improvements.

The proposal has been for [discussion](https://kusama.polkassembly.io/post/1942) here.

We were invited to participate in [AAG#11](https://twitter.com/polkawatch/status/1595083537107009537) where an interesting discussion followed

Community feedback has been incorporated to the proposal.

You can access the [detailed proposal](https://docs.google.com/document/d/1ljvYDuazbNBgjf94yFUbUEdeyBN5ixG6BXAEKxuxmL4/edit?usp=sharing) here.

Note: an extraordinary fee related to re-submission costs has been included.

- Polkawatch has launched decentralization analytics on Kusama and now supports Nomination Pools.
- The community is becoming more aware of the need for effective decentralization in the ecosystem.
- Parachains are secured by the relay chain but are still vulnerable to censorship, and Polkawatch aims to bring parachain support to their service.
- The proposal has been discussed and community feedback has been incorporated.
- An extraordinary fee related to re-submission costs has been included in the proposal.

[Replacement for Referenda #2] Polkawatch Decentralization Analytics Parachain Support and Continued Operation. 

Dear Community,

Ordum is a public good grants aggregator for the Polkadot and Kusama ecosystems. This proposal addresses the funding of R&D.

Introduction

There is no existing software besides Gitcoin to publish, apply for and manage grants. Gitcoin focuses on a quadratic funding model, while there is a need for an overall indexer and management software for grants in web3.

After reading the Builders Program post(https://forum.polkadot.network/t/builders-programs/226) on the Polkadot Forum and speaking with other members of the community (including councillors, Web3 Foundation, and members of Shokunin Network), it was evident that a grants aggregator is imperative for bringing projects into the ecosystem as well as scaling it.

In order to construct a rich and independent environment of public goods and DAOs, it is fundamental for teams to easily find and acquaint themselves with treasuries and foundations.

Problem

Treasuries / foundations(eg. Polkadot Treasury) are burning funds as there are not enough projects to support. 

Grants information and guidelines within the ecosystems are scattered and therefore difficult to find (there are only 2 places where we have a somewhat overview of these; Polkadot/Kusama documentation and Web3 Foundation Github). 

It is difficult to publicly track (grant) funding for different stages of project development. This has previously resulted in conflicts within the community.

There isn’t a unified public record to privately / publicly manage and display a grant recipient’s quality and outcome of delivery (scattered documentation). 

With GOV2 incoming, further research is required on tracking proposals and deliverables in order to determine the appropriate UX. 

Solution

Success for Ordum is the deliverance of all milestones and a V1 POC of a public goods grant aggregator.

1. A dapp which contains all grants from the ecosystems.

    Index data from treasuries in the ecosystem by building custom APIs(Subsquids) for tracking proposals 
    Integrate Github in the front end for tracking and submitting non-treasury grants 
    Building and maintaining light clients for quick data retrivals, security and low loading times 
    Enable log in with multiple DID services, Github and Wallets 

2. Minting of non-transferable NFTs as “certificates” for completed milestones. Each token would contain information on what was executed and how it was evaluated.

    Ordum will be built on Phala to leverege the chains privacy capabilities and Phat smart contracts 
    Create a connection between DID (foundation)–> Phala Smart Contract–> Non-transferable NFT–>DID (recipient) 
    Design a custom type of RMRK non-transferable NFT, stored on Crust, containing reports from the foundations on milestone delivery 

3. Delivery of milestones, grant applications and funding are displayed on a team’s profile for transparency.

    Front end displaying funding amounts and certificates within a roadmap

4. Issuing surveys and analyzing / feedback data for the purpose of aggregating and managing treasury grants in the most optimal way.

    Design the optimal UX through collaboration with other teams in the ecosystem(interviews, surveys)

Requested funding 78,804 USD 
Kusama rate EMA7 as per 24th of November 2022: 25.24 (and reimburstment of submission and decision deposit)

The full proposal can be viewed [here](https://hackmd.io/@XyloDrone/Ordum)

We look forward to hearing your feedback.

Ordum is a software that helps people get money to build things for the internet. They want to make it easier for people to find and apply for grants. 

There are not enough projects to support, and grant information is hard to find. 

Ordum will create a dapp that contains all grants from the ecosystems, and mint non-transferable NFTs as certificates for completed milestones. 

Delivery of milestones, grant applications, and funding will be displayed on a team's profile for transparency. 

Ordum will also issue surveys and analyze feedback data to manage treasury grants in the best way.

 Treasury Proposal: Ordum | Public Good Grants Aggregator for Polkadot and Kusama 

Hey everyone,

I would like to propose this new referendum today as an amendment and follow-up on the previous [referendum #308](https://kusama.subsquare.io/referenda/308).
As stated before in referendum #308, the intention of the referendum is the promotion of 6 collators to invulnerables, these being:

- TurboFlakes
- LuckyFriday
- ParaNodes
- Polkadotters
- Stake.Plus
- IcebergNodes

The referendum was successfully executed on [block #20691161](https://kusama.subscan.io/block/20691161?tab=event&event=20691161-2), but unfortunately, not all colators were promoted as intended.

After recapping my steps when creating the previous referendum, I realized that I must have made a mistake when manually creating the preimage. The issue on the [original call](https://kusama.subscan.io/referenda_v2/308) falls on two of the six collators being duplicated and two others missing.

After discussing the issue with my peers, I would like to present this referenda to the community today. It intends to fix the previous issue and promote LuckyFriday and ParaNodes to invulnerables on Asset-Hub Kusama as per the intention of the previous referendum.

Once again, apologies to LuckyFriday and ParaNodes for wrongly being missed on the previous call.

And thank you all for your time and vote,
Paulo


- Paulo is proposing a new referendum to fix a mistake made in a previous referendum (#308).
- The previous referendum aimed to promote 6 collators to invulnerables on Asset-Hub Kusama.
- However, not all collators were promoted as intended due to a mistake in manually creating the preimage.
- Paulo wants to fix the issue by promoting LuckyFriday and ParaNodes to invulnerables through this new referendum.
- Paulo apologizes to LuckyFriday and ParaNodes for the mistake and thanks everyone for their time and vote.

Executed

staking_admin

[Fix 308] Expand invulnerables set on Asset-Hub Kusama

This is a tip created by the [tip-bot](https://github.com/paritytech/substrate-tip-bot/).

### Details

- **Repository:** [polkadot-sdk](https://github.com/paritytech/polkadot-sdk)
- **PR:** [#1985](https://github.com/paritytech/polkadot-sdk/pull/1985)
- **Contributor:** [eagr](https://github.com/eagr)
- **Tip Size:** medium (16 KSM)


BigTipper

Hey everyone,

I’m proposing this referendum today, it aims to fix the only XCM instruction that failed to execute from the successful outcome of [referendum 224](https://kusama.subsquare.io/referenda/224). 

**Brief Summary**
The previous referenda 224 was all about decentralizing the collator set on both system chains  – Bridge-hub Kusama and Asset-hub Kusama with a call tabled with five XCM instructions. From these five instructions, four were successfully executed and only the call related to the expansion of the invulnerables set on Asset-Hub Kusama failed to execute. The reason for the failed instruction was due to the fact of missing onchain session keys from one of the collators by the time the referenda moved into the execution phase.

At the time, knowing that the runtime v1000000 would bring new extrinsics to better handle such cases and also facilitate add/remove invulnerables, was than discussed by all parties involved that would make sense to wait until the current runtime was active on chain to propose a new referenda that would fix the previous XCM instruction, and such referenda could also be used as an opportunity to try out the new extrinsic – collatorSelection.addInvulnerable. 

As a result I’m proposing this referendum asking the community to vote on it.

**What to expect from this referendum**
With the successful outcome we could expect the following:

- 6 new invulnerables, changing the total number from 2 to 8 (Note: the following list of collators were the ones already previously selected on referenda 224)
TurboFlakes: `H1tAQMm3eizGcmpAhL9aA9gR844kZpQfkU7pkmMiLx9jSzE`
LuckyFriday: `HPUEzi4v3YJmhBfSbcGEFFiNKPAGVnGkfDiUzBNTR7j1CxT`
ParaNodes: `J11Rp4mjz3vRb2DL51HqRGRjhuEQRyXgtuFskebXb8zMZ9s`
Polkadotters: `EPGHRDFaBbQz4uF8DgnuScxYp4rvvtpL5MTed7VvGprNQmm`
Stake.Plus: `E5G5qLNBF7nwhemokqNrNwUCQ7oHrLsBVjSc7XhTdRq8672`
IcebergNodes: `Eicei1RVHvqHBPJAY2fZpLy2KtCMjY7Kwjo3svjmGLH7FmT`

- 3 out of the 9 active permissionless collators will automatically switch to invulnerables with the remaining 6 keeping their active slot.

Thanks for your vote and time
paulo // apps.turboflakes.io


- A proposal is being made to fix a failed instruction from a previous referendum.
- The failed instruction was related to expanding the invulnerables set on Asset-Hub Kusama.
- The reason for the failed instruction was due to missing onchain session keys from one of the collators.
- The proposal asks the community to vote on adding 6 new invulnerables, changing the total number from 2 to 8.
- 3 out of the 9 active permissionless collators will automatically switch to invulnerables with the remaining 6 keeping their active slot.

[Fix 224] Expand invulnerables set on Asset-Hub Kusama

Due to an issue in the recent [decommissioning of Governance 1.0 on Kusama](https://github.com/paritytech/polkadot/pull/7314), which was enacted via [Referendum 301](https://kusama.subsquare.io/referenda/301), deposits associated with Treasury spend proposals remain locked. This referendum seeks to slash Kusama Gov 1.0 treasury deposits and refund the corresponding amounts to their respective proposers in a batch call similar to [Referendum 73](https://polkadot.subsquare.io/referenda/73), which was previously submitted on Polkadot.
Please note that spam proposals numbered 291, 292, 293, 294, and 296 have been identified as invalid submissions. Consequently, any bond associated with these proposals, as well as older proposals rejected by the council, are not included in this `forceBatch` call.

- There was a problem with a recent change to Kusama's governance system.
- This caused deposits for spending proposals to be locked.
- A new referendum has been proposed to refund these deposits to their proposers.
- Some proposals were identified as invalid and will not be included in the refund.
- This is similar to a previous refund on Polkadot.

OpenGov Referenda