candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

whitelisted_caller

- Kusama is being upgraded to Relay Chain 9381 and System Parachains 9382.
- The upgrade includes XCM v3, which helps different parts of the network communicate.
- Some changes will happen automatically, even if one part fails.
- Messages will be sent to Statemine and BridgeHub to prepare for the upgrade.
- The XCM version will be updated to 3 after 600 blocks (about 1 hour).
- Be careful with money-related actions during the upgrade.
- The upgrade will happen at block 17,335,450, around 11:00 UTC on April 4.
- The upgrade files are from specific GitHub releases.

Executed

WHO: Kusama

WHAT: Upgrade to Relay Chain 9381 and System Parachains 9382 releases, including upgrade to XCM v3.

PRICE/TIMEFRAME/RESOURCES: N/A

Kusama Runtime Upgrade 938*

- Five parachains requested HRMP channels with Statemine.
- The proposal includes transferring 10 KSM from the Treasury to Statemine.
- It also opens HRMP channels from Statemine to each parachain and back.
- The parachains involved are Amplitude, MangataX, Imbue, Tinkernet, and GM Parachain.
- Each parachain has a unique ID (e.g., Amplitude is 2,124).
- The encoded call details can be found [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x18041418020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300004c080000e8030000009001003c074c080000e8030000e80300000090010018020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300003e080000e8030000009001003c073e080000e8030000e80300000090010018020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e803000049080000e8030000009001003c0749080000e8030000e80300000090010018020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300004d080000e8030000009001003c074d080000e8030000e80300000090010018020c0402006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000b00a0724e18093c07e80300004b080000e8030000009001003c074b080000e8030000e803000000900100).

The proposal aims to accept and open return channels for five parachains by executing a batch call for each of them, including a forcetransfer of 10 KSM from the Treasury to Statemine sovereign account. The encoded call can be found in the provided link.

A New Batch Of HRMP Channels: Amplitude, MangataX, Imbue, Tinkernet, GM Parachain.

Remove Old Runtime Upgrade Preimage

- The proposal updates system parachains to version 9381.
- The main change is the introduction of XCM v3.
- It was named "v9381" instead of "v9380" due to late changes.
- The Relay Chain will now use XCM v3 to communicate with system parachains.
- The upgrade is set to happen 600 blocks after authorization.
- Release notes can be found in the Cumulus repository.

Cancelled

WHO: The proposal is made by the Cumulus team.

WHAT: The proposal updates system parachains to v9381 and introduces XCM v3.

PRICE/TIMEFRAME/RESOURCES: No information provided.

System Parachains 9381 Upgrade

- Kusama is upgrading to runtime v9380, which includes important updates like XCM v3.
- The upgrade allows the Auction Admin track to use a scheduler.
- The proposal hash is wrapped in a whitelist call, and the call data can be found on Polkadot.js.
- Some changes are pending audits, while others are already audited or considered trivial.
- The proposal is submitted through the Whitelisted Caller track and has been whitelisted by the fellowship.
- If approved, the changes will take effect at block #17,119,600.
- Users are encouraged to vote on the proposal.

Rejected

The proposal aims to upgrade Kusama to runtime v9380, including XCM v3. The upgrade is pending non-critical audit and will enact in block #17,119,600. The proposal is submitted in Whitelisted Caller track. No price or timeframe/resources mentioned.

Runtime Upgrade v9380 for Kusama

A proposal has been made to upgrade Kusama to runtime v9380. This upgrade includes XCM v3 and allows Auction Admin to use the scheduler. The proposal hash is wrapped in a whitelist call, and the call data can be found on Polkadot.js.org. The proposal is submitted in the Whitelisted Caller track, meaning the Fellowship will vote on a whitelist of the proposal hash. Some of the changes in this upgrade are:

1. Westend state trie to version 1
2. Allow duplicate topics in smart contract events
3. Scheduler is already at v4
4. Xcm v3
5. Enable treasury.spend by root origin for Polkadot network before gov2
6. Allow auctionadmin to use scheduler
7. Fix countedmap::set to take counter into account
8. Deprecate random interface in contracts
9. Correct arithmetical semantic of perdispatchclass
10. Add proof size to weight output
11. Migrate new benchmarking syntax
12. Remove uncles related code

Remember to vote on this proposal at your convenience.

The proposal aims to upgrade Kusama to runtime v9380, including XCM v3. The upgrade allows Auction Admin track to use scheduler. The proposal is submitted in Whitelisted Caller track. The price, timeframe, and resources are not specified.

- A new update called v9370 was released for parachains.
- It adds OpenGov origins to Statemine.
- There are links to authorize upgrades for Statemine and Bridge Hub.
- A link is provided to send something from Kusama.
- There are steps to submit and open referendums for Fellowship and public calls.
- These steps involve preimages and whitelisting calls.
- Links are given to decode and understand these actions.

Parachains v9370 release adds OpenGov origins to Statemine. No information is provided regarding price, timeframe, or resources.

Upgrade System Parachains to v9370

### Summary of Acala Foundation Parachain Issue

- **Acala Foundation** won a parachain slot auction with para id 2233.
- They intended to use this slot to renew Karura's lease.
- Due to a misunderstanding of the lease swap process, an incorrect wasm was submitted for para 2233.
- This mistake locked the parachain, preventing the swap.
- **Mangata team** faced a similar issue with their parachain.
- A proposal was made to swap leases between Karura (2000) and Acala's bid (2233), and between Mangata's operational parachain (2110) and their crowdloan parachain (2256).
- Efforts are being made to improve the lease renewal process to prevent future issues.

The proposal aims to perform lease swaps between Acala Foundation's para id 2233 and Karura para lease, and between Mangata's para ids 2110 and 2256. The goal is to resolve the issue of invalid wasm and enable the parachains to be used. The proposal also aims to design a better lease renew process for parachains to prevent similar situations in the future. No information on price/timeframe/resources is provided.

Lease swap for Karura and Mangata

- Kusama auctions are scheduled using a tool called the Scheduler Pallet.
- Two proposals, Ref 72 and Ref 81, were set up incorrectly, causing too many auctions to happen too quickly.
- The solution is to cancel these proposals and submit new ones with the correct settings.
- Three new proposals are being worked on to fix the issue:
  1. Cancel the incorrect auctions and Ref 81.
  2. Set up a new auction for Ref 81 to give more time for voting.
  3. Fix all auctions in Ref 72 and the last part of Ref 81.
- The first proposal to cancel the incorrect auctions is already submitted and needs votes.
- A special proposal is also needed to make sure the fix works properly.
- Everyone is encouraged to vote on these proposals to fix the problem.

WHO: Kusama community.

WHAT: Cancel Ref 72 and Ref 81 proposals and resubmit them on-chain due to misconfiguration.

PRICE/TIMEFRAME/RESOURCES: Not specified.

Kusama Auctions: Third time’s a charm - STEP 1

- This proposal is about upgrading Kusama to version v9370.
- It includes improvements like setting a minimum commission for staking and better contract address creation.
- Some updates fix issues, like unstaking accounts with penalties.
- The upgrade also adds new features, like better handling of NFTs.
- The community needs to approve this upgrade.
- A special group called the Fellowship will also check and approve the upgrade.
- Everyone in the Kusama community can vote on this proposal.

The proposal aims to upgrade Kusama to v9370, which includes improvements to staking admin track, contract address derivation, and weights. The proposal is submitted as a referendum in OpenGov and requires approval from the Kusama community and the Fellowship.

Runtime Upgrade on Kusama to v9370

- The Kusama community plans to schedule more auctions for parachains in 2023.
- They aim to have 57 auctions by January 2024.
- Auctions will happen in different lease periods (LP27 to LP35).
- Each lease period will have a specific number of auctions.
- The first two auctions for LP27 have already happened.
- A proposal is up for vote to approve this plan.
- People can review and vote on the proposal.

The Kusama community proposes to schedule 57 auctions from LP27 to LP35 until January 2024. The proposal includes the number of auctions for each LP and can be found in the provided link. The proposal is up for a vote on the whitelisted caller track.

New Batch of Auctions for 2023: from LP27 to LP35

- A new proposal wants to make parachains safer by checking runtime upgrades before they happen.
- Validators will test and agree on the upgrade before it is used.
- This idea has already been tested successfully on Versi, Rococo, and Westend.
- It helps reduce risks, especially for slashing (penalties for bad behavior).
- Parachains need to support a signal called `go_ahead_signal`.
- Links are provided to review and vote on the proposal.
- The proposal is ready for voting, so people can check and vote when they want.

The proposal enables pre-checking for runtime upgrade on parachains. Validators must compile and agree on the new runtime before it can be upgraded. This reduces the risk of unjustified slashes and has been successfully tested. Parachains need to support the `go_ahead_signal`. The call to be enacted and the fellowship proposal to be approved are provided.

Setting pvfCheckingEnabled In The Configuration To TRUE

### Bridge Hub (BH) Parachain Proposal

- **Purpose**: To add a Bridge Hub (BH) parachain to Kusama.
- **Function**: Acts as a gateway between Kusama and other networks like Polkadot and Ethereum.
- **Current State**: Contains basic logic but lacks bridge-specific features.
- **Future Plans**: Bridge-specific pallets will be added in future upgrades.
- **Primary Role**: Serves as a message routing system within Kusama and between other networks.
- **Example Use**: Parachains can route messages to the BH for handling cross-network communication.
- **Expected Impact**: Once operational, it will enable more interaction between Kusama and Polkadot.
- **Goal**: To get approval from Kusama stakeholders and establish a "shell" for bridge teams to develop their logic.

The proposal is to add a Bridge Hub (BH) parachain to Kusama, acting as a message routing system between Kusama and other networks. The BH will not contain bridge-specific pallets, but will allow bridge teams to focus on releasing their bridge logic. The goal is to get approval from Kusama stakeholders and launch a "shell" operational. Once operational, a Polkadot<>Kusama bridge will allow more interaction between the networks. No price, timeframe, or resources are mentioned.

[Whitelisted Caller] Referendum #53 - Add Bridge Hub System Parachain

[Whitelisted Caller] Referendum #50 - Upgrade Statemine v9360

Enable conditional fast-unstake service in Kusama

- A new proposal wants to schedule 4 auctions for Kusama.  
- One auction was lost during a migration, and two were left from LP27.  
- The community will vote on a new schedule for 2023.  
- The proposal is part of OpenGov and needs approval from the Kusama community.  
- The Fellowship is voting to whitelist the proposal hash.  
- People are encouraged to vote and ask questions if needed.  
- The proposal hash is `0x85928b2b75ffadbfbd4e321f46183cb33f5a3b68baaca0ebf62d4695a01d0070`.  
- More details can be found in the release notes.

The proposal aims to schedule 4 new auctions and a new schedule for 2023 for the Kusama community to vote on. The proposal is submitted as a referendum in OpenGov and requires approval and whitelisting by the Fellowship. No specific price, timeframe, or resources mentioned.

Proposal replacing the last 4 auctions on Kusama (until LP27) due to them failing on dispatch queue.

- Kusama is upgrading to version v9360.
- The upgrade includes changes from version v0.9.35 to v0.9.36.
- Some updates help with staking and warnings.
- There are fixes for rate limits and logs.
- The community needs to approve the upgrade.
- The Fellowship must whitelist the proposal.
- Everyone can vote on the upgrade.

The proposal suggests upgrading Kusama to v9360, including changes in runtime and miscellaneous areas. The proposal is submitted as a referendum in OpenGov, and the Kusama community needs to approve it.

Runtime Release v9360 for Kusama

- Encointer is resubmitting a runtime upgrade after fixing issues with past referendums.
- The upgrade allows participants to unregister from ceremonies, reducing no-shows and improving security.
- It also lets trusted users endorse new participants, helping the community grow.
- The upgrade updates dependencies to polkadot-0.9.28.
- The proposal has been whitelisted by the fellowship and is now up for a public vote.
- The community is asked to vote in favor of the upgrade to make it happen.

Encointer proposes a runtime upgrade v12 which allows participants to unregister from ceremony cycles and allows reputables to endorse newbies. The proposal calls for the dispatch of the whitelisted call, which has already been whitelisted. The public referendum has been started to execute the proposal.

Encointer runtime upgrade v12 2nd try

- Kusama is being upgraded to fix issues from a past event on 09.12.2022.
- The upgrade includes changes to how validators are treated when slashed.
- Some small updates are being made, like renaming crates and removing old code.
- A new function is added to check if an asset exists.
- The upgrade also includes changes to how messages are handled in the system.
- Two proposals will be voted on: one by the community and one by the Fellowship members.

The proposal aims to upgrade Kusama to v9350 to fix the last action point in the plan to relieve validators from slash events on 09.12.2022. The upgrade includes several runtime and miscellaneous changes, and the proposal is submitted to the Whitelisted Caller Track. No price/timeframe/resources mentioned.

Runtime Release v9350 for Kusama

This is a referendum whose proposer address (FkNMbSDe5vdfoaWGVS4FVtuVPSeiXjvcQew9tde6JNFUKd6) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Moonriver Council proposes to upgrade the Moonriver's runtime to version 2402, reducing the maximum concurrent votes for a given account on OpenGov to 20. No information on price/timeframe/resources.

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

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

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

REJECT - FAILED SUBMISSION

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

[1] Origin: WhitelistedCaller