candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

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

### Proposal Summary

1. **Proposal Aim**: Upgrade Polkadot’s runtime to version 9320.
2. **Issue**: The proposal will fail due to a code change in the scheduler pallet that prevents `set_code` from executing.
3. **Solution**: An external motion (306) has been opened to cancel the current proposal.
4. **Changes**: The proposal includes updates to various pallets and improvements to documentation and benchmarks.
5. **Release Notes**: Detailed changes can be found in the release notes for versions 0.9.31 to 0.9.32.
6. **Proposal Hash**: `0xbd78d3542767047aba0babb8c8825a5799e3ef54a21193ffe24b98eb4f895162`.
7. **Voting**: Requires both Council and community votes after the Council approves.
8. **Verification**: Use SRTool to verify the proposal hash.

[PLEASE REJECT] Runtime v9320 Upgrade On Polkadot

- 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

- 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

### Summary of Polkadot Staking Changes

1. **Nomination Pools**: Polkadot is introducing nomination pools to simplify staking for DOT holders.
2. **Current System**: Nominators can stake a minimum of 10 DOTs, with a limit of 50,000 nominators. The top 22,500 are chosen for rewards.
3. **Active vs. Waiting**: Nominators are either active (in the top 22,500) or waiting.
4. **Goal**: Encourage waiting nominators to join pools and prevent new waiting nominators.
5. **Proposed Change**: Increase the minimum stake requirement to 100 DOTs to discourage waiting nominators.
6. **Buffer**: Keeping some waiting nominators is beneficial for security.
7. **Pool Recommendation**: Nominators with less than 50 DOTs should be directed to join pools.
8. **Original Discussion**: For more details, see the [original post](https://polkadot.polkassembly.io/post/1224).

Proposal: Slightly higher nomination limits

- 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

Upgrade of Kusama runtime to v2029

Upgrade of Kusama Runtime to v2028

- Motion 234 is about upgrading Kusama Runtime to version 2026.
- It has a medium priority, meaning it should be done soon.
- The upgrade fixes logging issues with names that have dashes.
- It stops using old substreams that are no longer needed.
- It makes some RPC functions unsafe for better security.
- Council members are asked to vote on this upgrade as soon as possible.
- More details and the release notes can be found on GitHub.

Upgrade of Kusama Runtime to v2026 

- Motion 229 increases the number of validators by 1 every 6 hours for 100 eras.
- It was created because Referendum 88 passed but couldn't be executed due to a technical error.
- The motion was proposed to address the issue until a new feature (damping function) is tested and ready.
- The number of repetitions was reduced from 400 to 100 to help manage the waiting list of validators.

Motion 229 replacing Referendum 88 - validators increase.

### Moonriver Runtime Upgrade Summary

1. **Upgrade Proposal**: The Moonriver Council plans to upgrade the runtime to version 1502.
2. **Included Changes**: This upgrade includes the Runtime 1500 proposal and two additional fixes.
3. **Staking Update**: Pending revoke/decrease delegations will no longer receive staking rewards.
4. **EIP2612 Addition**: EIP2612 (Permit) for ERC20/XC20 precompiles is added, enabling gasless transactions.
5. **Orbiter Program**: Preparation for the Orbiter program, which aims to support the community and decentralize the network.
6. **Verification Hash**: The Blake2_256 hash for verification is `0xdc6eca875ce9decb206b0440e407694502bda293b0766dd5428eacba4eb03aa4`.

Runtime Upgrade 1502 - Moonriver Network

### Summary of Proposal

- **Objective**: Open a bi-directional channel between Moonriver and Khala to transfer MOVR and PHA tokens.
- **Token Registration**: Register PHA as xcPHA on Moonriver with specific details (multilocation, decimals, name, symbol).
- **Asset ID and Address**: xcPHA has a unique asset ID and XC-20 address.
- **Proposal Details**: Proposal #86 with a specific hash is submitted for approval.
- **Technical Steps**: 
  - Open and accept HRMP channels between the two chains.
  - Execute extrinsics on the relay chain to facilitate cross-chain transfers.
- **Prerequisite**: The parachain's sovereign account must have at least 10 KSM for collateral and execution fees.

Open/Accept HRMP channel to/from Khala and Register PHA Asset

SetCode: Kusama Runtime v2024 upgrade.

SetCode: Kusama Runtime 2023

Cancelling scheduled increase of validators slots at 600 for metrics review

SetCode Kusama Runtime 2022

- **Referendum 71** was a past event that passed on block 3,200,000.
- A new **motion** is proposed to fast-track the same design as Referendum 71.
- The proposal aims to **increase the number of validators** by 2 every 3600 blocks (1 era).
- This increase will happen **336 times**, taking about **3 months**.
- By the end, the total validators will be **x + 672**, where **x** is the starting number.
- If **Referendum 69** passes, the total will be **1172**; if not, it will be **1072**.
- If network stability or economics are harmed, the increase can be **canceled** using a specific ID.

Gradual Validator Count Ramp-up (+672 Validators/~3 Months) - same as Referendum 71 (read below)

SetCode, Kusama runtime 2019

SetCode, Kusama runtime 2015

### Summary of Migration Error Fix

- Alexander Popiak found an error in a Kusama Democracy migration.
- Old storage items under `Democracy.VoteOf` were not cleaned up.
- A motion was opened to remove the storage prefix via a Root call to the System pallet.
- The storage prefix is `0xf2794c22e353e9a839f12faab03a911b02a7afbcd5cd4ad2c68bbc63279ae52e`.
- This prefix is a combination of `xxhash("Democracy") + xxhash("VoteOf")`.
- The prefix is not used in the democracy pallet.
- The error was due to a typo in the migration code.

Clean up `Democracy.VoteOf` storage in Kusama

New runtime upgrade, v2012

- We need more registrars to keep the ecosystem safe and balanced.
- The council should focus on both community building and security.
- Liebi updated their registrar proposal based on council feedback.
- The new proposal looks better after recent discussions and changes.
- Motion 164 was submitted for the council to vote on this proposal.
- If passed, the community will vote on it next.
- The proposal aims to add redundancy and improve the registrar role.
- You can see the updated proposal here: [link](https://hackmd.io/@WUwOYEcKS7SDniXXxl93yA/ryqHRsDaI).

Tech. Comm. Proposals