candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Limit on the maximum number of validators, based on scaling issues

Backfilling the winners map on 2nd auction, repairing the Auction state.

Runtime v9070 on Kusama Network

Runtime v9050 on Kusama Network

Runtime v9040 on Kusama Network

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

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

Failed proposal

Configuration change requested by Technical Committee

Authorization of runtime upgrade: Statemine

setStorage for Statemine + fix for UMP queue configuration

Runtime v9030 on Kusama Network

Untitled - public proposal #47

### Moonriver Council Proposal Summary

1. **Upgrade Proposal**: The Moonriver Council plans to upgrade the Moonriver runtime to version 1801.
2. **Included Changes**: This upgrade includes the changes from Runtime 1800 and additional fixes.
3. **Runtime 1800 Details**: You can find more information about Runtime 1800 [here](https://github.com/PureStake/moonbeam/releases/tag/runtime-1800).
4. **Fixes in Runtime 1801**: The fixes included in this upgrade are detailed [here](https://github.com/PureStake/moonbeam/releases/tag/runtime-1801).
5. **Verification Hash**: The Blake2_256 hash for verification is `0x1dd8a942765d78ec1cc9b3e5e695167656726105b8b275c682087e6983bb245d`.
6. **Best Practices**: It is recommended to verify the hash of the proposal using srtool.

Runtime 1801 Upgrade

Authorize Staking precompile and smart contract interaction

- 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

- 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

- Runtime v2030 on Kusama

- The Litentry registrar is a service that helps verify users' identities automatically using cryptography.
- It checks if users own their email, Element, and Twitter accounts by sending them special links.
- Once users confirm the links, the service confirms their ownership and removes their data for safety.
- The service uses secure tokens to make sure only the right user can verify their accounts.
- If the connection to the system gets lost, it automatically reconnects to keep things running smoothly.
- Users get simple instructions to click buttons or links to complete the verification.
- This service makes the verification process faster, cheaper, and easier for users.

A registrar service on Kusama focusing on automatic verifications

Upgrade of Kusama runtime to v2029

- The proposal suggests changing Kusama's currency by making 100 KSM equal to 1 new KSM, similar to what was done with DOT.
- This change would make calculations easier and avoid using small decimals.
- Kusama currently uses two more decimals than DOT, making it harder to compare the two.
- Redenominating Kusama would make it simpler to compare with DOT, like comparing apples to apples.
- However, changing Kusama's currency is very complicated and requires a lot of work, especially since transfers are already enabled.
- The main focus right now should be on deploying parachains, which are very important for the DOT ecosystem.
- The proposer regrets suggesting the change, as it could cause confusion and is not a priority at this time.
- They ask if it’s possible to add this feature in the future when it’s more convenient.

Now is not the Time; Vote Against This Proposal 

### Summary

- **Proposal**: Open a bi-directional channel between Moonriver and Shiden.
- **Purpose**: Facilitate the transfer of MOVR and SDN tokens between the two chains.
- **Asset Registration**: Register SDN as xcSDN with specific details (multilocation, decimals, name, symbol).
- **Technical Steps**:
  - Moonriver will propose to open and accept HRMP channels with Shiden.
  - Shiden will accept the HRMP channel from Moonriver.
  - Execute extrinsics on the relay chain to set up the channels.
- **Asset Details**: xcSDN will have a specific asset ID and XC-20 address.
- **Execution**: Use XCM messages to manage asset transfers and channel setup.

Open/Accept HRMP channel to/from Shiden and Register SDN Asset

### Wasm Smart Contracts Bounty Proposal

- **Purpose**: Encourage WebAssembly smart contract development on Polkadot parachains.
- **Initiators**: A coalition of teams.
- **Objectives**:
  - Create audited Ink!/Ask! smart contract showcases.
  - Develop an incubation program.
  - Build a React Hooks library called "UseInk".
- **Approval Process**: 
  - Council approval required first.
  - Followed by a community vote via Referendum.
- **Budget and Details**: Available on the bounty page [here](https://polkadot.polkassembly.io/bounty/19).
- **Preimage Status**: Submitted but not yet paired due to application issue.
- **Proposal Hash**: `0xad5bd919076c71a6acba8ffafe12dfaf8ef83e40d69a56ee1ae1d5ffaa9f429e`.

Approval of Wasm Smart Contracts Bounty - bounty 19

Upgrade of Kusama Runtime to v2028

- This proposal is about whether to keep a human verification step for identity checks on Kusama.
- If the proposal passes, it will add a comment on the blockchain saying to keep human verification.
- Not voting means agreeing to remove the human check.
- The human verification is currently done twice for each identity check, but it might be reduced or removed.
- Reasons to remove it: it takes time, automatic checks are now good enough, it costs more, and users might prefer lower fees.
- If people value the human check, alternatives will be considered.
- The decision might also affect Polkadot.

Democracy Referenda