candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Rejected

staking_admin

[Invalid: Vote Nay] Staking Controller Account Deprecation

Executed

small_tipper

SmallTipper

- Subscan is a tool that helps people explore and understand the Kusama network.
- It costs a lot to keep Subscan running, including servers, security, and people.
- They are asking for money from the Kusama treasury to cover costs from January 2023 to March 2024.
- They worked hard to reduce costs in 2023 and saw good results, like cutting their Google Cloud bill by over 50%.
- They added new billing details for October 2023 to March 2024 to show costs are growing slowly.
- The Kusama network hasn’t paid for Subscan in 15 months, which is causing financial problems.
- If they don’t get funding, they might have to stop adding new features, which could hurt the Kusama ecosystem.
- They are asking the community for support to keep Subscan running smoothly.

big_spender

Subscan proposes to be reimbursed for operation and maintenance fees from the Kusama treasury from January 2023 to March 2024. The proposal includes billing information covering October 2023 through March 2024, with ongoing block production growth naturally increasing GCP expenses. The proposal aims to ensure the continuous operation and maintenance of Subscan, which serves as a vital block explorer and analytics tool within the Substrate ecosystem. The cost of the proposal is not specified.

Subscan | Infrastructure Costs of Subscan for Kusama & Asset Hub (Kusama) Networks (from January 2023 to March 2024)

- The Dots Magazine is a fun and easy-to-understand news media about Polkadot, a crypto ecosystem.
- It was started by two Polkadot fans in 2020 who wanted to share news and educate people about Polkadot.
- They use memes and humor to explain complex crypto topics in a simple way.
- The team includes John Mental and Mantra, who are both active in the Polkadot community.
- They have already gained 1.1k Twitter followers and created videos and interviews about Polkadot.
- They are asking for funding to make more professional content and help the Polkadot community grow.
- They have not received any money so far and are working as enthusiasts.
- Their goal is to make Polkadot more fun and accessible for everyone.

small_spender

WHO: John Mental and Mantra, Polkadot enthusiasts and content creators.

WHAT: The Dots Magazine, a non-nerdy entertainment news media that educates people about Polkadot and its ecosystem updates in an easy language using memes and humor.

PRICE/TIMEFRAME/RESOURCES: Requesting 235.4209 KSM ($10,000) for 6 months of operational work, with a working hour rate of $30 for 14 hours per week (including expenses on part-time production team), totaling 336 hours.

TheDots – The First Polkadot Non-Nerdy Media Outlet & Memes

whitelisted_caller

Enable Coretime

### Kusama Async-Backing Referendum

- **Purpose**: Enable faster block production for parachains.
- **Current Status**: Async-backing logic is active but in sync mode, producing blocks every 12 seconds.
- **Proposed Change**: Parachains can choose to produce blocks every 6 seconds.
- **Testing**: Successfully tested on Rococo and Westend since late 2023.
- **Dependencies**: Requires the upcoming `v1.2` runtime release.
- **Known Issues**: Some validators need to upgrade to avoid backing issues.
- **Action Required**: Validators should ensure their network keys are persistent to avoid discovery issues.

The proposal enables async backing on Kusama, allowing parachains to produce blocks at a faster rate of 6s. This is not mandatory, and they can still run at 12s. No critical issues are known, and the proposal won't change anything regarding that. The referendum will be enacted after the upcoming v1.2 runtime release.

Enable async backing on kusama

Upgrade Kusama v1.2.0

Register Coretime Parachain

### Summary

- **Proposal**: Increase backing timeout from 2s to 2.5s and approval-voting timeout from 12s to 15s.
- **Rationale**: To ensure a smoother experience for async backing parachains.
- **Details**: Found in [GitHub issue #3565](https://github.com/paritytech/polkadot-sdk/issues/3565).
- **Call Details**: Available [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-kusama.luckyfriday.io#/extrinsics/decode/0x332e0c01002000000600c4090000000000000601983a000000000000).
- **Parameter Adjustment**: `MaxMemoryPage` param is reset to its previous value.
- **Testing**: Conducted locally with zombienet and on Rococo.

WHO: The proposal is made by an unknown individual or group.

WHAT: Increase the backing timeout on validators from 2s to 2.5s and approval-voting timeout from 12s to 15s.

PRICE/TIMEFRAME/RESOURCES: No information provided.

Bump parachain validation timeouts

- A referendum is moving 25,000 KSM (about 10% of the Kusama Treasury) from the Relay Chain to Asset Hub.
- It sets the KSM asset rate to 1, meaning 1 KSM equals 1 KSM.
- This move requires special permission (root privilege).
- Once moved, the Treasury can operate normally on Asset Hub using Treasurer and XSpender tracks.
- Moving funds to Asset Hub enables new Treasury features, like staged spends.
- If successful, a similar proposal will be made for Polkadot.
- Polkadot could use more features like USDC/T spends and funding sub-treasuries.

WHO: Kusama Treasury

WHAT: Move 25k KSM from Relay Chain to Asset Hub, set asset rate of KSM to 1, enable new Treasury features

PRICE/TIMEFRAME/RESOURCES: Not specified.

Migrate 25k KSM to Asset Hub Treasury

A new tool is introduced to make creating and applying proposals in Kusama referendum v2 easier. It helps decide founding amounts, checks community interest, and finds similar proposals. You can try it at the provided link. Future plans include expanding to Polkadot, adding AI summaries, filters, better data extraction, success predictions, more statistics, and converting KSM to USDT. The tool requests 82 KSM for a 3-4 month period.

WHO: The proposer.

WHAT: Introducing a tool to simplify proposal creation and application process in Kusama referendum v2, with future plans to extend to Polkadot chain, add AI summary, filters, statistics, and KSM to USDT conversion.

PRICE/TIMEFRAME/RESOURCES: Requested amount of 82 KSM for an expected period of 3-4 months.

Proposal similarity

### Summary of Async Backing Referendum

- **Purpose**: Enable async-backing on Kusama, allowing parachains to produce blocks at a faster rate.
- **Current Status**: Async backing is already enabled in sync mode since v1.1.0, with a 12-second block production rate.
- **Proposed Change**: Parachains can choose to produce blocks at a 6-second rate after the referendum.
- **Testing**: Async backing has been tested on Rococo and Westend since late 2023, with successful migration to 6-second block rates.
- **Dependencies**: The referendum should be enacted after the v1.2 runtime release, which includes critical fixes.
- **Known Issues**: Some validators need to upgrade to avoid backing issues, and network key persistence is crucial for proper functioning.
- **Action Required**: Validators should upgrade to a version higher than 1.8 and ensure network keys persist across restarts.

TimedOut

WHO: Kusama network

WHAT: Enabling async backing on Kusama, allowing parachains to produce blocks at 6s rate instead of 12s rate.

PRICE/TIMEFRAME/RESOURCES: No information provided.

[Please reject] Enable async backing on kusama

- This proposal was made because Adam Steeber asked for more ideas for Kusama.  
- The goal is to create groups around ideas to reduce treasury spending.  
- It shows community support for ideas and allows for future discussions.  
- 50% of the treasury would go to bounties, cutting the burn rate by 50%.  
- Stake Plus won’t be involved in these groups.  
- The proposal also suggests creating a group to check if past projects met their goals.  
- Up to 50 people can join, with 4 auditors checking each project.  
- Reports will be made public to improve governance.

WHO: Up to 50 independent ecosystem agents.

WHAT: Establish a proto-collective tasked with auditing historical deliverables of Polkadot treasury proposals, ensuring proponents meet their obligations and safeguarding the treasury's assets.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Auditors Proto-Collective

- This proposal was made to support new ideas in the Kusama community.  
- It aims to create groups around ideas and reduce the treasury's spending.  
- The proposal suggests funding Twitch streamers who promote Polkadot during their streams.  
- Streamers could get $1,500 monthly for including Polkadot branding and games.  
- Curators helping with branding would be paid $125/hour plus expenses.  
- The goal is to support up to 60 streamers and encourage community involvement.  
- If no one leads the idea, the funds can be returned to the treasury later.

WHO: Polkadot ecosystem

WHAT: Establish a Proto Collective offering $1,500 monthly to Twitch streamers who integrate Polkadot branding into their streams and dedicate a portion of their streaming time to Polkadot games. Curators overseeing branding distribution compensated at $125/hour plus expenses, supporting up to 60 streamers.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Gamers Proto-Collective

- This proposal was made to help the Kusama community by creating bounties for new ideas.
- It aims to support ideas in principle and reduce the burn rate of the treasury by 50%.
- Stake Plus will not be involved in these new collectives.
- If someone wants to lead a collective, they should submit a full proposal with curators.
- The proposal also requests $75,000 from the Polkadot Treasury for a Regional Marketing Proto Collective.
- The funds will support up to 20 teams for creative marketing campaigns to promote Polkadot.
- Regional Marketing Directors will guide these efforts to increase Polkadot's visibility.

Regional Marketing Proto-Collective

- The proposal sets the minimum fee for an on-demand order to 0.005 KSM per block.
- This fee aims to prevent spam while allowing for affordable experimentation.
- If the fee is too high after the system goes live, a new proposal can be made to lower it.
- The proposal is on the Whitelisted Caller track, requiring approval from the Fellowship.

WHO: The proposal is not clear about who is proposing the change.
WHAT: Set the minimum fee for an order for a single block via the on-demand system to be 0.005 KSM.
FOR WHAT PRICE/TIMEFRAME/RESOURCES: The proposal does not mention any specific price, timeframe, or resources.

Setting onDemandBaseFee to 0.005 KSM

- A referendum is about choosing curators for a bounty.
- The bounty is for finding security bugs in the Polkadot and Kusama bridge.
- Curators will check how well the bounty works and decide rewards.
- They have different skills to help make the bounty successful.
- More information about the curators and what they will do is available in a document.

WHO: Curators
WHAT: Evaluate effectiveness and attribution of reward for Polkadot <> Kusama Bridge Security Bug Bounty
PRICE/TIMEFRAME/RESOURCES: Not specified

CURATORS PROPOSAL FOR BOUNTY 27 - POLKADOT <> KUSAMA BRIDGE SECURITY BUGBOUNTY

treasurer

Funding Brale integration into Kusama Asset Hub to introduce branded stablecoins (v3)

- The P<>K bridge charges fees from users on Asset Hub.
- It pays rewards to relayers from AssetHub's accounts on BridgeHub.
- These rewards are a big part of the bridge's costs.
- At first, the treasury will fund AssetHub's accounts on BridgeHub.
- They plan to start with 10,100 DOT and 2,030 KSM.
- Over time, user fees will cover the bridge's costs.
- Any extra money from fees will go back to the treasury.
- More details about funding can be found on GitHub.

WHO: The P<>K bridge

WHAT: Proposes an initial seed of 10100 DOT and 2030 KSM to be split among relevant system chain sovereign accounts for initial bootstrap runway to the bridge.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Fund system chains sovereign accounts on Kusama BridgeHub for Polkadot<>Kusama bridge

- A plan to fund a bridge between two systems (P<>K) was cancelled.
- The bridge charges fees from users and pays rewards to relayers.
- The initial funding was supposed to come from the treasury.
- 10000 DOT and 2000 KSM were proposed to start the bridge.
- The bridge should later cover its costs with user fees.
- The funds were to be handled by a trusted Polkadot Fellow.
- If this plan was rejected, a slower funding process would be used.
- The exact details of the funding can be found in a GitHub issue.

medium_spender

Request withdrawn - replaced by whitelisted caller #361

Kusama Runtime Upgrade v1.1.3

### Proposal Summary

- **Objective:** Create a "DAO factory" in the Kreivo parachain to help users conduct real-world businesses.
- **Duration:** 3 months (Q2).
- **Scope:** Focused on onboarding 5 to 10 new DAOs by the end of Q2.
- **Budget:** 175,500 USD for 9 full-time employees over 3 months.
- **Funding:** 3,333 KSM (equivalent to 168,449.82 USD).
- **Additional Work:** Contribute to the Polkadot protocol through governance improvements.
- **Long-term Goal:** Address social inequality through ongoing experiments and developments.

Virto proposes a 3-month budget of 175,500 USD to onboard 5-10 new DAOs and build the most powerful DAO factory in the ecosystem. The funds will also be used to contribute to the core Polkadot protocol via the technical Fellowship. They are asking for 3,333 KSM, equivalent to 168,449.82 USD.

Virto team Q2

Duplicate of #354 - please ignore

- 50 KSM was lost during a teleport from Bridgehub-Kusama to Kusama.
- The wrong call-data was used, causing a fatal error and the tokens were lost.
- The correct call-data was available but not used.
- The tokens did not get deposited anywhere and are lost in the system.
- The mistake was due to not double-checking the call-data.
- Developers are working on making such errors recoverable in the future.
- The 50 KSM was meant for a system-collator slot bid, which was not won.

We lost 50 KSM in a blockhole during a teleport call. We were trying to teleport 50 KSM from our account on Bridgehub-Kusama to Kusama.
We first tried with small amounts after we had found the right working call and then we thought copied the call-data to initiate the actual transfer, but it was an old copy that lead to the error of <code>unroutable</code>, which is a fatal error and the tokens get lost apparently in the system. We don't know where they get lost. You can see it in the <a href="https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fsys.ibp.network%2Fbridgehub-kusama#/explorer/query/0xbe5d33b166c6e839eba295c04c646c512bd715622ad8faf2287f1ea9d9f098ee">events</a> that the tokens don't get deposited anywhere. This is new information to us.
This is the call-data I have used: <code>0x1f0903000109030300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000</code>
This would have been the correct call-data: <code>0x1f090301000300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000</code>
Our request is to recover the 50 KSM from openGov to the account that made call.
<ul>
<li>The call was our mistake, we should have double checked.</li>
<li>There is work in progress by the core developers to make sure these errors are claimable in the future, but it's not in production yet.</li>
<li>The 50 KSM was on that account was to bid for a system-collator slot for bridgehub, which we didn't win. The teleport was one way until runtime upgrade <code>1,001,000</code></li>
</ul>

WHO: OpenGov
WHAT: Recover 50 KSM lost in a blockhole during a teleport call due to user error.
PRICE/TIMEFRAME/RESOURCES: Not specified.

OpenGov Referenda