candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

- The Council voted to fix an issue with Kusama's total issuance.
- Some KSM tokens were burned because of a problem with Statemine.
- A new update (v9040) will fix this issue and allow KSM to be counted again.
- The fix involves setting the balance of a special account to match the KSM in Statemine.
- The Council acted quickly to prevent more KSM from being lost during the fix.
- The Apps team will re-enable a feature called `teleport` after everything is fixed.
- This ensures that KSM tokens are properly accounted for and can be used again.

proposalHash

Evening up the total issuance on Kusama - XCM Pallet balance.

Failed proposal

Runtime v9040 on Kusama Network

Configuration change requested by Technical Committee

proposalId

VLN: Sube v1.0

Authorization of runtime upgrade: Statemine

setStorage for Statemine + fix for UMP queue configuration

Motion 302 is a proposal to upgrade the Kusama Shell to Statemine, the first common good chain on Kusama. The motion involves two steps: setting the Shell storage to the Statemine genesis and authorizing the runtime upgrade with a given code hash. To verify the preimage, follow these steps:

1. Download genesis values and open PolkadotJS UI.
2. Fill up information and check the encoded call hash.
3. Verify the call data used on the `xcmPallet.send` call using the Extrinsics tab on Polkadot js Apps.

If the call data hash matches the one on the screenshot, the motion hash should be the same as the Preimage hash for `xcmPallet.send`.

set the Shell storage to the Statemine genesis

The Technical Committee (TC) is working on a proposal to reduce the number of assignments by validators to parachains in order to minimize network issues. Currently, validators are overzealous in assigning to parachains, especially on Kusama. The TC aims to track the 40 parachain groups on the network by the next runtime upgrade to ensure finalization. This proposal changes the parachain configuration in advance to match an upcoming runtime change and will not affect current behavior. The preimage for this proposal can be found on Google Drive.

Runtime v9030 on Kusama Network

### Summary of Snowbridge Proposal

- **Project**: Snowbridge, a trustless and permissionless bridge between Polkadot/Kusama and Ethereum.
- **Objective**: To launch on the Bridge Hub, a common-good parachain developed by Parity.
- **Funding Request**: 28 months of operations (16 months retroactive, 12 months future).
- **Goal**: To become a common-good bridge on both Polkadot and Kusama.
- **Details**: Includes long-term roadmap, governance plans, and economic incentives.
- **Voting**: Both Kusama and Polkadot networks are voting on the proposal.
- **Kusama Proposal**: Available for community vote [here](https://kusama.polkassembly.io/referenda/1).
- **Next Steps**: If approved by the Council, it will go to the community for a vote.

Treasury Proposal: Snowbridge Funding Proposal

- **Klever Wallet** is a popular crypto wallet used by over 2.5 million people worldwide.
- It supports 10 blockchains, including Bitcoin, Ethereum, and Tron, with more being added.
- The wallet is available on iOS and Android and offers features like staking, swapping, and buying crypto.
- Klever wants to add support for **Kusama**, a blockchain in the Polkadot ecosystem.
- They are asking for funding to include Kusama in their wallet.
- Klever has 50 developers and a 24/7 support team to help users.
- The wallet is secure, with features like facial recognition and military-grade encryption.
- Klever plans to expand its features into the Polkadot ecosystem in the future.

Klever Mobile Wallet Inclusion of Kusama (Milestone one and two)

- OpenZeppelin specializes in secure smart contract development.
- They are proposing to review and audit the ink! smart contract language.
- The review will also cover Substrate’s smart contracts pallet.
- The goal is to improve security and the development experience.
- After the review, OpenZeppelin will provide a security assessment report.
- The full proposal can be found [here](https://docs.google.com/document/d/1GzQhvDY1jGeb-7_buNBwO4ppL0Siu-kTDktVQVDCg8g/edit?usp=sharing).

Proposal: ink! design audit by OpenZeppelin

- **Motion 295** is about canceling 115 slashes from era 2,249.
- A runtime upgrade (v9010) changed how elections work to make them more reliable.
- Some validators had trouble processing election solutions because of slow hardware or old software.
- This caused them to miss submitting heartbeats, making them appear offline.
- Many validators didn’t meet performance requirements, leading to liveness slashing.
- The motion asks for votes to decide if these slashes should be canceled.

slashIndices

 Cancellation of 115 slashes that happened in era 2,249

Untitled - motion 0x782f...2736

- The v9320 release of parachains is linked to the v9320 runtime of the Relay Chain.
- It includes minor updates to Assets and Uniques.
- "Anonymous" proxy is changed to "Pure" proxy.
- There are also some minor bug fixes.
- The release has specific actions like "Authorize Upgrade" and "Send from Polkadot."
- A proposal hash is provided for tracking the proposal.
- The proposal needs approval from the Polkadot Council and a community vote.
- Review and vote on the proposal when you can.

Statemint Runtime Upgrade to v9320

- A problem was found with Westend collators: blocks weren't being added every 6 seconds.
- The issue happened because Westend didn't have secondary vrf slots enabled, so non-primary blocks lacked randomness.
- A sudo transaction was sent to Westend to fix this by enabling secondary vrf slots.
- The same fix should be applied to Kusama if it works on Westend.
- A proposal is being made to change BABE's configuration on Kusama to use secondary vrf slots.
- This change should only happen after a runtime upgrade.
- The Technical Committee needs to consider this when planning the timing.
- A preimage for the proposal is available [here](https://drive.google.com/file/d/1P0nEgO0hJtfzp3JYkERQT5zze3KIWMy6/view?usp=sharing).

 Fix for issue found with collators on Westend, also in Kusama. 

Runtime v9010 on Kusama Network

The Validator Resource Center and Ranking Website (VRC) has entered Phase 2, which enhances the ranking method to better represent user preferences. The VRC score is now a major factor in the manual selection process, and new metrics have been added to reduce the information load on nominators. A new filtering technique helps to reduce the overall set of validators, making it easier for nominators to make appropriate selections. A staking dashboard has also been introduced, providing visual and numerical information about the network.

The proposal covers the development of milestones 6, 7, 8, 9, and 10. The majority of the work for these milestones has been completed, with the team finalizing details on M10 for further development. In Phase 2, the team extended previous work and incorporated three major upgrades:

1. A new manual selection for validators, taking into account custom scoring and a filtering technique to remove quantitatively dominated validators from the overall lists.
2. A dashboard that shows general information and graphs with metrics over time, making it easier to cope with the ever-changing nature of the network.
3. A process for nominators to cultivate their on-chain nominations by comparing past nominations to the most recent era and flagging critical events.

The proposal also includes a way to feature not-elected validators to incentivize their inclusion in the user's validator set. The final part of the VRC Development covers milestones 6 to 10, with a total estimation of EUR 4,000.00. Payment conditions include one submission per milestone, with subsequent milestones to be paid after delivery. The overall timeline is 5 weeks.

Validator Resource Center and Ranking Website for Kusama (Phase 2) - Milestones 6, 7, 8, 9, 10 (Final submission)

### Stylo Wallet Maintenance Proposal

- **Purpose:** Covers maintenance costs for Stylo Wallet, including general upkeep, upgrades, and infrastructure.
- **Networks:** Supports both Kusama and Polkadot, alternating every six months.
- **Duration:** Covers May to October 2021.
- **Amount Requested:** 2,880.00 EUR or 8.90 KSM.
- **KSM Rate:** 323 EUR/KSM (based on monthly average).
- **Frequency:** Submitted bi-annually.
- **Beneficiary Account:** `ESByNCnB6Q3p5VQVEcEMvQCk6y6ahuSEv22oxxrQ2ybfggr`.
- **Past Info:** Detailed past upgrades and budgets available [here](https://docs.google.com/document/d/18LI0BB5nnyhQJZW4-SdWOWy_Z6W3kObJUKSv53aU-fg/edit?usp=sharing).

Stylo wallet - recurring payment to cover maintenance costs

CryptoLocally is a global P2P exchange that allows people to trade cryptocurrencies without a middleman. They support many blockchain networks like Bitcoin, Ethereum, and more. They make it easy for everyone to use cryptocurrencies and DeFi by offering many ways to buy and sell them. CryptoLocally wants to help Kusama and Polkadot by filling gaps that other exchanges don't cover. They hope to be a part of this ecosystem for a long time. You can read more about their plan by clicking on the link provided.

CryptoLocally Kusama Integration Proposal

OnFinality is a SaaS platform that helps blockchain developers by providing infrastructure services for the Kusama/Substrate community. They recently launched a shared node API Service and are listed in the Polkadot.js app. They want to get funding to cover the costs of running two pools of Kusama nodes for Q2 2021. In Q1 2021, they served over 252 million requests. They will keep their free tier for users and maintain one-click deploy dedicated node access. You can access their public API service by creating a free account or connecting through Polkadot.js.

High Performance Public Infrastructure (Ongoing Costs for Q2 2021)

### Polkadot Runtime Upgrade Proposal

- **Proposal**: Upgrade Polkadot's runtime to version v9300.
- **Previous Issue**: Motion 286 replaced Motion 285 due to queue limitations.
- **Audits**: Several low-priority audits and trivial changes are pending or completed.
- **Proposal Hash**: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`
- **Process**: Requires Council vote followed by community referendum.
- **Verification**: Use SRTool to verify the proposal hash.
- **Action**: Community members should vote when the proposal reaches the referenda queue.

Council Motions