candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

### Encointer V12 + Statemine 9330 Upgrade

- **Purpose**: Upgrade Kusama's system parachains: Statemine and Encointer.
- **Encointer V12**: Adds new features and improvements. Details in [this post](https://kusama.polkassembly.io/post/2017).
- **Statemine 9330**: Introduces a new Assets API for asset class destruction. Allows state cleanup over multiple calls.
- **Proposal Calls**:
  - **Statemine**: `StatemineAuthorizeUpgrade` with data `0x0102957f0c9b47bc84d11116aef273e61565cf893801e7db0223aeea112e53922a4a`.
  - **Encointer**: `EncointerAuthorizeUpgrade` with data `0x0102ccdfc804e0482f951ef7ad15fda0d38ead81c42e93a8276e60a45c663b8a3b91`.
  - **Relay Chain**: `Batch XCM Send` with call hash `0x461c26edbf3148234fef402415fd55aa80add45abc3982578218d0b2f690141c`.
- **Whitelist Call**: `WhitelistCall` with hash `0x34fd5fdf54f9cfcfe8038d1aed183df0f84791878e29f0572d7c3b7d6d08f181`.
- **Dispatch Call**: `WhitelistedCallWithPreimage` with hash `0xc77ff5a4dd42ef33bad99104b6580c6cda9ff9c32086840d8492ed751d744893`.

Executed

whitelisted_caller

WHO: Kusama's system parachains, including Encointer and Statemine.

WHAT: Upgrade to Encointer V12 and Statemine 9330, adding new features and an Assets API for asset class destruction.

PRICE/TIMEFRAME/RESOURCES: Not specified.

[Whitelisted Caller] Referendum #17: Upgrade Statemine and Encointer Parachains

staking_admin

referendum_canceller

Moonbeam proposes to register Statemint USDC token as xcUSDC, an XC-20 token with the following details: Multilocation, Decimals, Name, Symbol, Asset ID, and XC-20 address. The proposal has been submitted through On-Chain Referenda #15 and the technical details are also provided. No information is given about the price/timeframe/resources.

- The proposal wants to upgrade Kusama's system to version v9340.
- It replaces an older proposal (referendum 254) that didn't work because of changes.
- The upgrade includes small fixes and improvements, like better handling of large assets and voting rights.
- Some changes are already checked and approved, while others are still being reviewed.
- The proposal uses a special method called `set_storage` instead of `set_code`.
- After the Council votes, the community will also need to vote on it.
- People can check the details and verify the proposal using tools like `SRTool`.

The proposal aims to upgrade Kusama's runtime to v9340, which includes various low-level changes. The proposal is submitted as an external motion and requires community voting. No information is provided regarding the price, timeframe, or resources required for the upgrade.

Runtime v9340 Upgrade On Kusama: Fixing OpenGov Parameters and more! (Replacing referendum 254 on Gov1, which failed to execute)

Cancelled

REJECT - FAILED SUBMISSION

### Substrate-API-Client

- **Purpose**: Connects to a Substrate-based node via RPC.
- **Alternative**: Alternative to `subxt`.
- **Importance**: Essential for Rust developers working with Substrate parachains.
- **Features**:
  - Supports `no_std` environments.
  - Facilitates extrinsic creation in trusted hardware (e.g., Intel SGX).
  - Potential for IoT applications.
- **Interface**: Easy-to-use with practical examples.
- **Proposal**:
  - Maintenance and support for 3 months (Nov-22 to Jan-23).
  - Evaluation and design of two new features:
    - CLI wallet implementation.
    - Full `no_std` compatibility.

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

Approved

big_spender

WHO: The proposal is made by the substrate-api-client team.

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

PRICE/TIMEFRAME/RESOURCES: The funding is required for 3 months (Nov-22 until Jan-23). The cost is not mentioned in the summary.

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

- The post requests a top-up for the Moderation Team Bounty.
- The top-up is needed due to current market conditions.
- Changes have been made to the initial proposal.
- Details and spending analysis are available in a linked document.
- The original bounty top-up post is also linked for reference.
- The community is thanked for their attention.

treasurer

WHO: The community.

WHAT: Requesting a top-up to the Moderation Team Bounty to continue funding their contributions and support.

PRICE/TIMEFRAME/RESOURCES: Details can be found in the proposal linked.

Treasury Proposal: Moderation Team Bounty Top-up

- Encointer has a new update that lets people leave ceremony cycles, which helps reduce no-shows and makes things safer.
- Now, anyone who has proven they are real can help new people join, not just special helpers. This helps more people join easily.
- The update also improves the system's technology to work better with Polkadot.
- Encointer wants a special group called the fellowship to check and approve this update because it's important and needs expert review.
- There are steps to follow for the fellowship to approve the update, including voting and checking the changes.
- The process involves creating and checking special codes and making sure everything is safe and correct.
- After the fellowship approves, everyone else can vote on the update too.
- This whole process helps make sure the update is good and safe for everyone using Encointer.

TimedOut

Encointer proposes a code upgrade that allows participants to unregister from ceremony cycles, allows reputables to endorse newbies, and upgrades dependencies to polkadot-0.9.28. They would like their runtime upgrade to be whitelisted by the fellowship, and the decision period for the fellowship whitelist referendum is 7 days. The submission deposit for the public referendum is 100KSM, and the decision deposit is 33.333 KSM.

Encointer runtime upgrade v12

- Kintsugi parachain stopped making new blocks because of a problem with how long each block takes to make.
- A fix has been found and tested with help from Parity.
- No one's money is lost or at risk right now.
- To fix Kintsugi, the Kusama community needs to vote on a special update.
- The problem is only with Kintsugi, no other parachains are affected.
- Until fixed, no new kBTC can be made, and no money can be moved on Kintsugi.
- Exchanges and other parachains have been told to stop certain activities until Kintsugi is fixed.

Kintsugi parachain stopped producing blocks due to a Kintsugi-specific issue with the slot duration in Aura. The only way to recover the chain is via a Kusama governance proposal. The Kusama community is asked to vote on recovering the Kintsugi parachain as soon as possible. No user funds are affected. The proposal is requesting the whitelist track for this proposal to accelerate recovery of Kintsugi. The estimated time and cost are not mentioned.

Emergency Proposal: Recover Kintsugi Parachain

### Summary of Math Crypto's Batch Delegation Guide

- **Purpose**: Provides a guide and tool for delegating all Gov2 tracks on Kusama to a single account in one transaction.
- **Resources**: Includes a [steps guide](https://www.math-crypto.com/opengov/batch-delegate/) and a [web page](https://backend-opengov.math-crypto.com/) with a delegation hash generator.
- **Benefit**: Simplifies the process for users who want to delegate multiple votes at once.
- **Proponent's Action**: The guide's proponent plans to use the new Gov2 system for a tip in an unused track.
- **Status**: Gov2 is operational and ready for use on Kusama.

big_tipper

WHO: Math Crypto

WHAT: Provides a batch delegation guide and web page with a delegation hash generator for OpenGov/Gov2 on Kusama.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Gov2 - Batch delegation step guide

### Summary of OpenGov Referendums

1. **Referendum 1 and 2**: Initially proposed but found to be unsuccessful due to the use of `treasury.ApproveProposal`, which requires root origin.

2. **Resubmitted Proposals**: The teams resubmitted their proposals using the `Treasurer` and `Big spender` tracks with the call `treasury.Spend`.

3. **New Referendums**:
   - **Referendum 3**: Funds the development of **Snowbridge**.
   - **Referendum 5**: Supports **Polkawatch**'s decentralization analytics and Parachain operations.

4. **Cancellation Service**: Uses the Referenda Canceller track to cancel Referendums 1 and 2, replaced by Referendums 5 and 6.

WHO: OpenGov
WHAT: Resubmitted Referendum 3 and 5 to fund Snowbridge and Polkawatch's operations respectively, using treasury.Spend call. Also cancelling Referendum 1 and 2.
PRICE/TIMEFRAME/RESOURCES: Not specified.

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

### Polkawatch Proposal Summary

- Polkawatch recently launched decentralization analytics on Kusama and added Nomination Pools support.
- The community is increasingly aware of the importance of decentralization, sparked by a recent deplatforming event of Solana nodes.
- Other teams, including wallets, parachains, and data scientists, are interested in accessing Polkawatch data to raise awareness in the ecosystem.
- Parachains, while secured by the relay chain, are still vulnerable to censorship from dishonest collators, network operators, or regulatory changes.
- This proposal aims to extend Polkawatch support to parachains, continue service operations, and make minor improvements.
- The proposal has been discussed and feedback has been incorporated.
- A detailed version of the proposal is available [here](https://docs.google.com/document/d/1ljvYDuazbNBgjf94yFUbUEdeyBN5ixG6BXAEKxuxmL4/edit?usp=sharing).
- An extraordinary fee for re-submission costs has been included.

Polkawatch proposes to bring parachain support to their decentralization analytics service, following interest from other teams in the ecosystem. The proposal includes continued operation of the service and minor improvements, with an extraordinary fee included for re-submission costs. No specific price, timeframe, or resources are mentioned.

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

### Ordum: Public Good Grants Aggregator

- **Purpose**: Ordum aims to create a public good grants aggregator for the Polkadot and Kusama ecosystems, focusing on R&D funding.
- **Current Issue**: Existing grant management tools like Gitcoin are insufficient for the needs of web3 ecosystems, leading to scattered information and difficulties in tracking funding.
- **Problem**: Treasuries and foundations have excess funds due to a lack of projects, and grant information is hard to find and manage.
- **Solution**: Ordum proposes a decentralized application (dapp) to index and manage grants, including features like custom APIs, light clients, and integration with Github.
- **Milestone Certificates**: Non-transferable NFTs will be minted to certify completed milestones, enhancing transparency and accountability.
- **Transparency**: Grant applications, funding, and milestones will be displayed on team profiles for public viewing.
- **User Experience**: Surveys and feedback will be used to optimize the UX for managing treasury grants.
- **Funding Request**: Ordum seeks $78,804 for development, with a Kusama rate of 25.24 as of November 24, 2022.

Ordum proposes to build a public goods grant aggregator for the Polkadot and Kusama ecosystems to solve the scattered information and lack of software for managing grants. They plan to create a dapp, mint non-transferable NFTs, display milestones and funding on a team's profile, and issue surveys for optimal grant management. They request funding of 78,804 USD and aim to deliver a V1 POC of the aggregator.

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

- A new proposal is being voted on for funding Snowbridge, a bridge between Kusama/Polkadot and Ethereum.
- The bridge will be trustless, permissionless, and work on the Bridge Hub parachain.
- The funding request is for 28 months of operations (16 months past, 12 months future).
- The goal is to launch Snowbridge as a common-good bridge on both Kusama and Polkadot.
- The full proposal has more details about the project, roadmap, and plans.
- Both Kusama and Polkadot networks are voting on this project.
- The proposal is now open for community voting.

WHO: Snowfork team, Parity, Kusama and Polkadot networks. 

WHAT: Develop a trustless, permissionless bridge between Kusama/Polkadot and Ethereum called Snowbridge. 

PRICE/TIMEFRAME/RESOURCES: Funding request for 28 months worth of long term runway for all operations for the Snowbridge team (16 months retroactive, 12 months in future). Full proposal can be reviewed on the post.

#3 [Replacement for Referenda #1] Treasury Proposal: Snowbridge Funding Proposal

### Summary of Post Content

- A referendum (#2) was initially unsuccessful because it required a specific permission (root origin) to enact.
- The proposal was resubmitted using a different method (treasury.Spend) and can be found [here](https://kusama.subsquare.io/referenda/referendum/5).
- Polkawatch, a decentralization analytics tool, was recently launched on Kusama and now supports Nomination Pools.
- The community is increasingly aware of the importance of decentralization, sparked by a recent deplatforming event of Solana nodes.
- Polkawatch aims to add support for parachains, which are secured by the relay chain but still vulnerable to censorship.
- The proposal for parachain support and other improvements has been discussed and can be found [here](https://docs.google.com/document/d/1ljvYDuazbNBgjf94yFUbUEdeyBN5ixG6BXAEKxuxmL4/edit?usp=sharing).
- Community feedback has been incorporated into the proposal.

Rejected

WHO: Polkawatch team

WHAT: Bring parachain support for Polkawatch, continued operation of the service, and other minor improvements.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Polkawatch Decentralization Analytics Parachain Support and Continued Operation. [this proposal will not enact successfully if approved: more info below]

### Snowbridge Proposal Summary

- **Project**: Snowbridge by Snowfork team.
- **Objective**: Develop a trustless, permissionless bridge between Kusama/Polkadot and Ethereum.
- **Location**: Bridge Hub, a common-good parachain developed by Parity.
- **Funding**: Request for 28 months of operations (16 months retroactive, 12 months future).
- **Goal**: Launch as a common-good bridge on both Polkadot and Kusama.
- **Details**: Extensive roadmap, governance, economic plans, and incentives included in the full proposal.
- **Voting**: Both Polkadot and Kusama networks are voting on the project.
- **Hash**: `0xfae1763e293099ff7858ddf848255fb05efb10b973f49886b5b213b2981fb111`.

Snowfork team proposes to develop a trustless, permissionless bridge between Kusama/Polkadot and Ethereum called Snowbridge. They request funding of 28 months worth of long term runway for all operations, retroactive for 16 months and 12 months in the future, to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama. The proposal is up for vote by both networks.

OpenGov Referenda

Referenda Tracks