candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Upgrade of Kusama Runtime to v2027

I just test how the proposal on the chain connects to polkassembly

### Moonbeam Runtime Upgrade to Version 1504

- **Security Issue**: A security problem was found and reported through Moonbeam's Immunefi bug bounty program.
- **Upgrade Proposal**: The Moonbeam Council suggests upgrading to runtime version 1504 to fix the issue.
- **Fix Details**: The upgrade will restore DELEGATECALL for Ethereum standard precompiles and smart contracts, but keep it disabled for custom precompiles.
- **Release Note**: More information about the upgrade can be found in the release note on GitHub.
- **Security Announcement**: Detailed information about the security issue is available in a blog post.
- **Bug Bounty Program**: Learn more about Moonbeam's bug bounty program on Immunefi.
- **Verification**: The Blake2_256 Hash for the proposal is `0xadf9d791567b5170326a535af19d2fec6b8d3931cca1083a625b6aeb58e75c0d`.

Runtime Upgrade 1504 - Moonriver Network

- A bug in Kusama caused some candidates to lose their bonds unfairly.
- The bug has been fixed, and now it's time to refund those affected.
- Motion 239 is about giving money back to the candidates who lost their bonds.
- A special code was used to check and make sure everything is correct.
- The refunds will be done all at once using a batch process.
- The community needs to vote to approve this motion.
- Council members are asked to vote when they can.

Incorrect Slashing on Council Caused by elections-phragmen Pallet Bug

A proposal to gradually increase the number of validators

- The proposal suggests changing the value of KSM (Kusama) to match DOT (Polkadot).
- It would increase KSM units from 10 million to 1 billion, making 1 old KSM equal to 100 new KSMs.
- The change doesn’t affect the total value or ownership of KSM, just the way it’s counted.
- Developers say this change would require a lot of work and could cause confusion.
- The proposal isn’t necessary for Kusama’s network to work well or for auctions to happen.
- Kusama is already running smoothly, unlike Polkadot when it made a similar change.
- The main goal is to make KSM easier to use and calculate, like DOT.
- The proposal doesn’t change the smallest unit of KSM, called Planck.

Redenomination KSM for better parallel chain slot auction testing.（The revision：I'm sorry about my proposal ）

- 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 

- The proposal suggests changing the KSM (Kusama) denomination by increasing its total amount by 100 times.
- Current KSM balances will also increase by 100 times (1 old KSM = 100 new KSMs).
- The distribution of KSMs stays the same, so everyone keeps the same share of the network.
- The precision of KSM will change from 12 decimal places to 10 decimal places.
- The smallest unit of KSM, called Planck, remains unchanged.
- The change makes calculations easier, similar to what happened with Polkadot's DOT.
- The proposal only changes what is called a "KSM" and doesn’t affect the network technically.
- The system remark is a special note encoded in the proposal.

Proposal for redenomination of KSM

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

- The proposal is inspired by Polkadot and adjusted for Kusama.
- It suggests slowly adding more validator slots over time.
- The plan is to increase slots by 1 every 6 hours (1 era).
- This increase will repeat for 400 eras.
- The goal is to avoid a sudden jump in validators.
- The network aims to reach up to 1000 validators gradually.

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

- Kusama version 0.9.19 changed how weight is converted to KSM for fee payments.
- Before 0.9.19, the conversion rate was 0.27 KSM per unit of weight.
- After 0.9.19, the rate is now about 0.41 KSM per unit of weight.
- This update affects the XCM-Transactor, which needs to be adjusted.
- The new conversion rate is 0.41485177350 KSM per weight.
- A proposal (#17) has been made to update this value.
- The proposal uses a specific function to set the new conversion rate.

Set new relay transactor info in Moonriver

### Summary of Proposal to Register xcUSDT on Moonriver

- **Objective**: Register USDT from Statemine as xcUSDT on Moonriver.
- **Details**:
  - Multilocation: `{ "parents": 1, "interior": {"X3": [ { "Parachain": 1000}, {“PalletInstance”: 50},{ "GeneralIndex": 1984 }]}}`
  - Decimals: `6`
  - Name: `Tether USD`
  - Symbol: `xcUSDT`
- **Asset ID**: Extracted from Tether’s official website.
- **Fee Calculation**: Based on the current KSM to USD price ratio.
- **Proposal Hash**: `0x0ea6d0cf368bc6f02a0397837a00b32f2bf25745a64ed9265cef0c4f8a0ff535`
- **Technical Steps**:
  - Register the asset using `assetManager.registerAsset`.
  - Store a revert code using `system.setStorage` for smart contract interaction.
- **Outcome**: xcUSDT will be assigned asset ID `133057993812922544048267207069832508503` and XC-20 address `0xFFFFffFf641a099723723c870F7368C47f96F457`.

Register USDT from Statemine as xcUSDT on Moonriver

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

### Summary of Proposal to Update XCM Version on Moonriver

- **Current XCM Version**: Kusama currently uses XCM Version 1 to communicate with Moonriver.
- **Proposed Update**: The proposal suggests updating the supported XCM version to Version 2.
- **Proposal Details**: The proposal is Proposal #17 with the hash `0x1fbe2211015409a8a4ab90235a19436e63690e333356e965f3f842389bb1ef31`.
- **Technical Steps**: 
  - Kusama expects Moonriver to respond to a Query ID with the supported version.
  - The Query ID can be verified using the chain state.
  - The update involves sending a XCM message with specific instructions.
- **Hex-Encoded Call Data**: The hex-encoded call data for the update is `0x67000101000204037929030200000000`.

Updated XCM Supported Version on Kusama

### Summary of HRMP Channel Proposal

- **Proposal Acceptance**: We propose to accept an HRMP (Horizontal Relay-routed Message Passing) channel between Bifrost (Kusama) and Moonriver.
- **Previous Failure**: The previous proposal failed due to improper execution on Kusama.
- **Main Use Case**: Initially, the channel will be used to transfer BNC tokens from Bifrost to Moonriver, with potential for other uses later.
- **Technical Execution**: The acceptance requires executing a specific extrinsic on Kusama, involving several steps like withdrawing assets, buying execution time, and transacting call data.
- **Collateral Requirement**: The parachain's sovereign account needs to hold at least 5 KSM as collateral and additional KSM for execution fees.
- **Proposal Details**: The proposal has a specific hash and call data, which can be viewed on Moonriver's extrinsic decoder.
- **Hex-Encoded Call Data**: The call data for accepting the channel is provided in hex format.

Accept HRMP Channel from Bifrost to Moonriver

SetCode: Kusama Runtime 2023

Cancelling scheduled increase of validators slots at 600 for metrics review

### Summary of Proposal to Register xcAUSD on Moonriver

- **Objective**: Register aUSD (Acala Dollar on Karura) as xcAUSD on Moonriver.
- **Details**:
  - **Multilocation**: `{ "parents": 1, "interior": {"X2": [ { "Parachain": 2000}, { "GeneralKey": "0x0081" }]}}`
  - **Decimals**: 12
  - **Name**: Acala Dollar
  - **Symbol**: xcAUSD
- **Fee**: Karura (KAR) fee for executing the XCM.
- **Proposal**: Proposal #79 with hash `0xc0d55701c24731f46df65f6feffdbd68acae2c4276b3b4c750cfdbd154ad4e40`.
- **Technical Steps**:
  - Register the asset using `assetManager.registerAsset`.
  - Store a revert code using `system.setStorage` for smart contract interaction.
- **Outcome**: xcAUSD will be assigned asset ID `214920334981412447805621250067209749032` and XC-20 address `0xFfFffFFfa1B026a00FbAA67c86D5d1d5BF8D8228`.

Register Acala Dollar from Karura as (xcAUSD) on Moonriver

SetCode Kusama Runtime 2022

### Summary of HRMP Channel Proposal

- **Proposal**: Accept an HRMP channel between Bifrost and Moonriver.
- **Initial Use**: Transfer BNC tokens from Bifrost to Moonriver.
- **Fast-Tracked**: Due to high block production times, the proposal was expedited.
- **Technical Steps**:
  - Execute acceptance in Kusama using specific extrinsics.
  - Use XCM messages to withdraw assets, buy execution time, and execute call data.
- **Collateral**: Requires ~5 KSM per channel direction, plus fees for XCM execution.
- **Referendum**: Referendum #77 with hash *0xb9a83527d40a4d28321346eb73e9ad5431d3cc82d7330a12fab098324f750f96*.

- **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)

- The proposal will add 2 validators every 3600 blocks (1 era) for 336 times.
- This will happen over about 3 months.
- At the end, there will be 672 more validators than the starting number.
- If the network has problems, the plan can be stopped using a special command.
- The plan was checked quickly but not fully tested.

Democracy Referenda