- A proposal wants to stop the upgrade of Polkadot to version 9320.
- This is because of changes in the FRAME code that affect how schedules work.
- There is a new check in the code to prevent exceeding weight limits for blocks.
- Most functions will work fine, but the `set_code` function will not pass this check.
- This is due to `set_code` using the maximum block weight, which always fails the check.
- A new proposal will be made with the correct call soon.
- The Council must approve this motion before the community votes on it.

proposalHash

votingPeriod

delay

This proposal aims to cancel the upgrade of Polkadot Runtime to v9320, due to a change on FRAME code explained below:

As the dev team works on transforming all FRAME pallets and code to work properly with WeightsV2, they have added the following check to the scheduler pallet: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107)

This piece of code should ensure that we don't execute a scheduled call that would use more weight than we have left for the block. For most calls this isn't any problem as they should be fit easily into a block. However, for `set_code` the dev team currently has annotated it with using the max block weight: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 ](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 )

So, when trying to execute `set_code` with the scheduler it will always fail this check. There will be already some consumed weight when trying to dispatch the call and `some_weight + max_block_weight` will always be bigger than `max_block_weight`. A new proposal will be submitted with the correct call soon.


 - Proposal hash: `0x88998cf7535c1f22d62849be8464fdc38fe46c0a46dc943ec56c91ef6592ec65`

 - Preimage is submitted. 

- Note this motion is an external one: meaning if/after Council approves, the community will vote on this proposal with the final decision.

Cancel the upgrade of Polkadot Runtime to v9320

- There is a proposal to change the number of nomination pools in Polkadot.
- Right now, there are a maximum of 64 nomination pools allowed.
- The proposal wants to increase this limit to 128 nomination pools.
- This change is suggested because everything is working well so far.
- If the Council agrees, the community will have a chance to vote on it later.
- The proposal is measured by a special code called a hash.

![](https://i.ibb.co/ZM5JWMB/Screenshot-2022-12-06-at-10-07-36.png)

Proposal hash: `0x98b3a8aa425c1e1ca5cd96d1b8f3491233b0745575e648a8c5497e83cec76f16`

The proposal aims to **lift the limits imposed on the nomination pools**, which limited the number of nomination pools to **64** in Polkadot, preventing any potential risk if there had been any bugs or issues with the launch. Given that everything works as expected, the new limits are to be increased to **128** total pools. Please note that as this is an external motion, if the Council approves, the community will vote after in the referenda queue for the final decision.

Increasing Max Number of Nomination Pools

- There are almost 50,000 nominators involved in a project.
- A new motion is being proposed to improve nomination rules.
- This motion wants to set higher minimum bond limits for nominations.
- There's already a vote for a different proposal called Referendum 86.
- If the new motion is approved, it could replace Referendum 86.
- The goal is to make changes quickly and keep nominations easy.
- More information about why the new limits are important is available online.

As we are almost at 50k nominators and we need to avoid a scenario of no one being able to change or set nominations, this external motion aims to outstrip [Referendum 86](https://polkadot.polkassembly.io/referendum/86) aiming to define slightly higher nomination min bond limits, which is currently up for community vote for next 11 days and with a new motion suggest shorter voting and enactment periods. If approved and later fast-tracked by the TC, making [Referendum 86](https://polkadot.polkassembly.io/referendum/86) redundant; Hence, this proposal, along with updating several staking configurations, would also cancel the [Referendum 86](https://polkadot.polkassembly.io/referendum/86). 

Further information about the importance of the higher nomination min bond limits can be found in the initial discussion post [here](https://polkadot.polkassembly.io/post/1224). 

 ![](https://i.postimg.cc/cJJQF6CT/Screenshot-2022-12-02-at-09-24-23.png)

Redefining Slightly Nomination Minimum Bond Limits and Removing Max Number of Nominators (replacing Referendum 86)

- A new proposal has been made to cancel an earlier one that is expected to fail.
- The failure is due to recent changes in the code that will not allow the scheduled call to execute properly.
- Developers are working to update the code so that everything functions correctly.
- A new proposal will be submitted soon that should work better.
- The proposal aims to upgrade Polkadot to a new version called v0.9.32.
- There are several minor changes and fixes included in this upgrade.
- After the Council votes on the proposal, the community will also need to vote on it.

This proposal will fail in enactment, so [external motion 306](https://polkadot.polkassembly.io/motion/306) is now opened to cancel this. A change on FRAME code explained below is the reason this will fail: as the dev team works on transforming all FRAME pallets and code to work properly with WeightsV2, they have added the following check to the scheduler pallet: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/scheduler/src/lib.rs#L1105-L1107)

This piece of code should ensure that we don't execute a scheduled call that would use more weight than we have left for the block. For most calls this isn't any problem as they should be fit easily into a block. However, for `set_code` the dev team currently has annotated it with using the max block weight: 

[https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 ](https://github.com/paritytech/substrate/blob/b1396f708b2001593d5589dd1bd3f832821fb208/frame/system/src/lib.rs#L404-L405 )

So, when trying to execute `set_code` with the scheduler it will always fail this check. There will be already some consumed weight when trying to dispatch the call and `some_weight + max_block_weight` will always be bigger than `max_block_weight`. A new proposal will be submitted with the correct call soon.

Please note this proposal should be rejected.

______________________
_______________________
_______________________

The proposal aims to upgrade Polkadot’s runtime to [v9320](https://github.com/paritytech/polkadot/releases/tag/v0.9.32): more information can be found on the release notes.


**Runtime**

- [S] ✅ trivial [#12358](https://github.com/paritytech/substrate/pull/12358) Low - Remove contracts rpcs
- [S] ✅ trivial [#12421](https://github.com/paritytech/substrate/pull/12421) Low - Adapt `pallet-contracts` to weightv2
- [S] ✅ audited [#11649](https://github.com/paritytech/substrate/pull/11649) Low - Bound uses of `call`
- [S] ✅ trivial [#12429](https://github.com/paritytech/substrate/pull/12429) Low - Contracts: adapt dry-run runtime apis to weightv2
- [S] ⏳ pending non-critical audit [#12282](https://github.com/paritytech/substrate/pull/12282) Low - Maximum value for `multiplierupdate`
- [P] ✅ trivial [#6021](https://github.com/paritytech/polkadot/pull/6021) Low - Maximum value for multiplierupdate
- [S] ✅ trivial [#12334](https://github.com/paritytech/substrate/pull/12334) Low - Macro stubs for all pallet:: macros to improve documentation visibility and discovery + revamp of pallet macro documentation
- [S] ✅ audited [#12109](https://github.com/paritytech/substrate/pull/12109) Low - Vesting pallet - make `withdrawreasons` configurable
- [P] ✅ audited [#5451](https://github.com/paritytech/polkadot/pull/5451) Low - Manual para lock
- [P] ✅ trivial [#6155](https://github.com/paritytech/polkadot/pull/6155) Low - Add `force_open_hrmp_channel` call
- [P] ✅ trivial [#6171](https://github.com/paritytech/polkadot/pull/6171) Low - Bump transaction_version (0.9.31)
- [S] ✅ trivial [#12558](https://github.com/paritytech/substrate/pull/12558) Low - Update `pallet-multisig` benches
- [P] ✅ trivial [#6189](https://github.com/paritytech/polkadot/pull/6189) Low - Update weights, attempt two (0.9.31)

This release also contains the changes **from v0.9.31 to v0.9.32**: 
- [Substrate#12630](https://github.com/paritytech/substrate/pull/12630): Make `--database` cli argument case insensitive again.
- [Substrate#12632:](https://github.com/paritytech/substrate/pull/12632): Fixes a bug with the transaction pool after doing a warp sync.
- [Substrate#12633](https://github.com/paritytech/substrate/pull/12633): Fixes the `payment_queryInfo` RPC to be compatible with the latest runtime changes.


Proposal hash: `0xbd78d3542767047aba0babb8c8825a5799e3ef54a21193ffe24b98eb4f895162`

You can review the hash and changes in the release notes and use SRTool to verify proposal hash - make sure to vote at your convenience! This proposal is submitted as an **external motion**: meaning after Council vote, the community will need to vote on the proposal in referenda queue.

[PLEASE REJECT] Runtime v9320 Upgrade On Polkadot

- A new proposal is for a project called **Snowbridge** that connects Polkadot/Kusama and Ethereum.
- The project is developed by the Snowfork team and aims to be trustless and permissionless.
- It will be launched on a special parachain called the Bridge Hub.
- The proposal requests funding for 28 months to support the Snowbridge team's work.
- This includes 16 months of past work and 12 months for future work.
- If the proposal is approved, both Polkadot and Kusama communities will vote on it.
- More details about the project are available in the full proposal linked in the document.

Original Proposal: [HERE](https://polkadot.polkassembly.io/treasury/192).

The proposal is now up for vote! aiming to cover the development of **Snowbridge** by the Snowfork team: a fully trustless, permissionless and general purpose bridge between Polkadot/Kusama and Ethereum. The bridge will launch on the Bridge Hub, a common-good parachain that is being developed by Parity for Kusama and Polkadot. This proposal is a funding request for 28 months worth of long term runway for all operations for the Snowbridge team (16 months retroactive, 12 months in future), with the goal to launch as a common-good bridge on the Bridge hub on both Polkadot and Kusama.

The full proposal can be reviewed on [the post](https://polkadot.polkassembly.io/treasury/192) and includes extensive additional details related to further motivation for supporting and promoting Snowbridge, a long term roadmap, governance and economic plans as well as long term economic incentives for successful execution, launch and running of the project. Please note that both networks are voting on the project: the Kusama proposal (up for vote by the community on OpenGov) can be found [here](https://kusama.polkassembly.io/referenda/1). 

If approved by Council, this proposal will be up for vote after by the community in referenda queue. @Councillors: please review and vote at your convenience!

Proposal hash: 0xcb7a0584b5d85d6065d2e492d476aa1c1b92b9a0e492aa668b33036671500ddb

Treasury Proposal: Snowbridge Funding Proposal

- There is a new update for parachains called "v9320."
- The update includes some small changes and bug fixes.
- The word "Anonymous" has been changed to "Pure" in the proxies.
- Two links are given for authorizing upgrades and sending from Polkadot.
- A proposal hash is provided for reference.
- The proposal needs to be approved by the Polkadot Council first.
- After approval, the community will vote on the proposal.

The parachains [v9320 release](https://github.com/paritytech/cumulus/releases/tag/parachains-v9320) contains updates that correspond to the v9320 runtimes of the respective Relay Chain. Changes to Assets and Uniques are minimal, but the release includes the change of “Anonymous” to “Pure” proxy and minor bug fixes.

\- [Authorize Upgrade](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x0102f02ab4af6b1b58da2805d186f87ca03e808dc0d93d3581b4dbdab4785bea95cb)

\- [Send from Polkadot](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x630001000100a10f0204060202286bee880102f02ab4af6b1b58da2805d186f87ca03e808dc0d93d3581b4dbdab4785bea95cb\))

\- Proposal Hash: 0x1c3e581368a6762a6ecc26903a1fd18345bc212df09e8a66222778def7fcf49d

This proposal is submitted as an external motion: meaning that if/after the Polkadot Council approves, the community will vote on the proposal in referenda queue for the final decision. 

Make sure to review and vote at your convenience!

Statemint Runtime Upgrade to v9320

Polkadot is introducing nomination pools to simplify staking for DOT-holders. Currently, nominators can stake a minimum of 10 DOTs and up to 50,000 nominators can participate. The top 22,500 are chosen for each era's election process and may receive staking rewards. Nomination pools aim to make staking easier and are designed to address two main concerns:

1. Encourage waiting nominators to join pools, which is mainly a task for Wallet/UI development.
2. Prevent too many waiting nominators from being created, as most may prefer joining pools instead.

To achieve these goals, the minimum nomination limit could be increased to 100 DOTs, based on the current requirement of around 200 DOTs to be an active nominator. This change would help prevent nominators from being created if they are likely to end up in the waiting queue. However, keeping a buffer of waiting nominators is important for Polkadot's economic security, so the 50,000 nominator limit should remain. With nomination pools, anyone with less than 50 DOTs should be directed to join pools instead, and their nominate transaction should be rejected.

Including contextual information form the staking team below - original discussion post [HERE](../post/1224). 

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Nomination pools are just around the corner for Polkadot, and this suggests some changes to be applied to the staking system.

First, let’s recap on the current status quo: Currently, nominators can freely set their intention to nominate in Polkadot, as long as they meet two limits: a minimum of 10 DOTs is staked, and a maximum of 50\_000 nominators is not filled. This creates a nomination market, where in every era, the top 22\_500 nominators from this open market are chosen to participate in the election process, and possibly receive staking rewards (if other conditions like over-subscription are not met).

This is a complicated and involved process. Nomination pools are exactly here to combat this and provide a simpler experience for DOT-holders to participate in staking.

Based on this, let’s cluster Polkadot nominators into two groups: **active** (in the top 22500), and **waiting**. The main concern at this point is to

-   Encourage all existing waiting nominators to join pools. This is mainly a task for the Wallet/UI development ecosystem, and is beyond the scope of this discussion.
-   Prevent too many waiting nominators to be created. The reason being that I speculate that most of these nominators have **erroneously** in the waiting queue, and prefer joining pools instead.

To achieve the second goal, we can set the nomination limits (10 DOTs, 50\_000) such that the system is not so _inviting_ to waiting nominators. In other words, the system should try and prevent nominators from being created, if they are certainly going to end up being in the waiting queue.

For example, we empirically know that the actual amount of DOTs needed to be an active nominator is around 200 DOTs as of this writing. Therefore, we can set the minimum nomination limit to a higher value such as 100.

Note that keeping a buffer of waiting nominators is a positive factor for Polkadot's economic security. It allows for buffer of waiting nominators to be ready, should a (malicious) cluster of nominators decide to chill all at once, preventing nothing at stake issues. Therefore, I am not suggesting lowering 50\_000 as well, and find that a reasonable bound. But, with nomination pools, I do think we should immediately forward anyone with less than e.g. 50 DOTs to join pools instead, and the way to do that is to immediately reject their nominate transaction.

-   [https://polkadot.polkassembly.io/post/1224](../post/1224)

Proposal: Slightly higher nomination limits

- A proposal to upgrade Polkadot's system called "runtime" to version v0.9.30 has been made.
- The new proposal replaces an earlier one because there can be only one idea discussed at a time.
- The last proposal was about changing rules for special groups called nomination pools.
- There are several small tasks being worked on, like improving safety and making changes to how things are named.
- Some tasks have finished reviews, while others are still being checked.
- After the council votes, everyone in the community will also get to vote on this proposal.

The proposal aims to upgrade Polkadot’s runtime to [v9300](https://github.com/paritytech/polkadot/releases/tag/v0.9.30). More information about the release can be found on the link in this post. As the external queue can only hold one proposal at a time, yesterday's [motion 286](https://polkadot.polkassembly.io/motion/286), removing the limits on members in nomination pools, deleted previously approved [motion 285](https://polkadot.polkassembly.io/motion/285) aiming to upgrade Polkadot's runtime. This new proposal replaces motion 285.

**Runtime**

* [S] ✅ audited [#12170](https://github.com/paritytech/substrate/pull/12170) Low - Pallet-identity: be more paranoid ;)
* [S] ⏳ pending non-critical audit [#12222](https://github.com/paritytech/substrate/pull/12222) Low - Add constfeemultiplier to the transaction payment pallet
* [S] ⏳ pending non-critical audit [#11981](https://github.com/paritytech/substrate/pull/11981) Low - Breaking: rename call & event
* [S] ✅ trivial [#11738](https://github.com/paritytech/substrate/pull/11738) Low - Add inspect trait for asset roles
* [S] ⏳ pending non-critical audit [#11806](https://github.com/paritytech/substrate/pull/11806) Low - Improve base weights consistency and make sure they're never zero
* [S] ✅ trivial [#12205](https://github.com/paritytech/substrate/pull/12205) Low - Add special tag to exclude runtime storage items from benchmarking
* [S] ⏳ pending non-critical audit [#12034](https://github.com/paritytech/substrate/pull/12034) Low - [feature] part 1: add targetlist for validator ranking
* [S] ✅ trivial [#12186](https://github.com/paritytech/substrate/pull/12186) Low - Contracts: use weakboundedvec for instrumented code
* [P] [#5535](https://github.com/paritytech/polkadot/pull/5535) Low - Runtime/disputes: slashing
* [S] ✅ trivial [#12258](https://github.com/paritytech/substrate/pull/12258) Low - Breaking: rename origin
* [S] [#12230](https://github.com/paritytech/substrate/pull/12230) Low - Bound staking storage items
* [S] ✅ trivial [#12083](https://github.com/paritytech/substrate/pull/12083) Low - Make automatic storage deposits resistant against changing deposit prices
* [S] ✅ trivial [#12283](https://github.com/paritytech/substrate/pull/12283) Low - Rename anonymous to pure proxy
* [P] ✅ trivial [#6037](https://github.com/paritytech/polkadot/pull/6037) Low - Increase blockhashcount parameter
* [S] ⏳ pending non-critical audit [#12329](https://github.com/paritytech/substrate/pull/12329) Low - Add base-weight to system::extrinsic* events
* [P] ✅ trivial [#6032](https://github.com/paritytech/polkadot/pull/6032) Low - Paras: unblock offboarding when pvf-check concludes
* [S] ⏳ pending non-critical audit [#12366](https://github.com/paritytech/substrate/pull/12366) Low - [feature] add deposit to fast-unstake
* [P] [#6050](https://github.com/paritytech/polkadot/pull/6050) Low - Add fast-unstsake pallet to all runtimes
* [S] ⏳ pending non-critical audit [#12277](https://github.com/paritytech/substrate/pull/12277) Low - Add storage size component to weights

Proposal hash: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`

You can review the hash and changes in the release notes and use SRTool to verify proposal hash - make sure to vote at your convenience! This proposal is submitted as an **external motion**: meaning after Council vote, the community will need to vote on the proposal in referenda queue. 

Runtime v9300 Upgrade On Polkadot

- Motion 286 is a proposal for Polkadot.
- It wants to remove limits on members in nomination pools.
- This change will help with the goals of Referendum 78.
- There was a mistake in the original proposal that didn't lift the limits.
- Voting on this motion is important for the community.
- Make sure to vote soon so it can be considered!

[**motion 286**](https://polkadot.polkassembly.io/motion/286) is up for vote! Please vote ASAP: this proposal removes the limits on members in nomination pools on Polkadot to fulfil the goal of the recently approved [referendum 78](https://polkadot.polkassembly.io/referendum/78). Preimage is submitted: The proposal had a mistake and did not lift the limit of maximum members per pool, therefore the pools are still unusable on Polkadot.

Make sure to vote soon on this external motion for the community to vote in referenda queue after!

Removing members' limit for the community to join nomination pools

- A new proposal is to upgrade Polkadot's system to version v0.9.30.
- The upgrades include many changes that are checked and almost ready.
- Some changes are about making the payments better and using storage wisely.
- There are new features related to ranking validators and fast-unstaking.
- The proposal has a special hash that you can check to see what changes are made.
- After the Council votes, the community will also need to vote on the proposal.

DELETED IN EXTERNAL QUEUE BY MOTION 286 - NOW REPLACED BY MOTION 287
_____________________________________________________________________________

The proposal aims to upgrade Polkadot’s runtime to [v9300](https://github.com/paritytech/polkadot/releases/tag/v0.9.30). More information about the release can be found on the link in this post.

**Runtime**

* [S] ✅ audited [#12170](https://github.com/paritytech/substrate/pull/12170) Low - Pallet-identity: be more paranoid ;)
* [S] ⏳ pending non-critical audit [#12222](https://github.com/paritytech/substrate/pull/12222) Low - Add constfeemultiplier to the transaction payment pallet
* [S] ⏳ pending non-critical audit [#11981](https://github.com/paritytech/substrate/pull/11981) Low - Breaking: rename call & event
* [S] ✅ trivial [#11738](https://github.com/paritytech/substrate/pull/11738) Low - Add inspect trait for asset roles
* [S] ⏳ pending non-critical audit [#11806](https://github.com/paritytech/substrate/pull/11806) Low - Improve base weights consistency and make sure they're never zero
* [S] ✅ trivial [#12205](https://github.com/paritytech/substrate/pull/12205) Low - Add special tag to exclude runtime storage items from benchmarking
* [S] ⏳ pending non-critical audit [#12034](https://github.com/paritytech/substrate/pull/12034) Low - [feature] part 1: add targetlist for validator ranking
* [S] ✅ trivial [#12186](https://github.com/paritytech/substrate/pull/12186) Low - Contracts: use weakboundedvec for instrumented code
* [P] [#5535](https://github.com/paritytech/polkadot/pull/5535) Low - Runtime/disputes: slashing
* [S] ✅ trivial [#12258](https://github.com/paritytech/substrate/pull/12258) Low - Breaking: rename origin
* [S] [#12230](https://github.com/paritytech/substrate/pull/12230) Low - Bound staking storage items
* [S] ✅ trivial [#12083](https://github.com/paritytech/substrate/pull/12083) Low - Make automatic storage deposits resistant against changing deposit prices
* [S] ✅ trivial [#12283](https://github.com/paritytech/substrate/pull/12283) Low - Rename anonymous to pure proxy
* [P] ✅ trivial [#6037](https://github.com/paritytech/polkadot/pull/6037) Low - Increase blockhashcount parameter
* [S] ⏳ pending non-critical audit [#12329](https://github.com/paritytech/substrate/pull/12329) Low - Add base-weight to system::extrinsic* events
* [P] ✅ trivial [#6032](https://github.com/paritytech/polkadot/pull/6032) Low - Paras: unblock offboarding when pvf-check concludes
* [S] ⏳ pending non-critical audit [#12366](https://github.com/paritytech/substrate/pull/12366) Low - [feature] add deposit to fast-unstake
* [P] [#6050](https://github.com/paritytech/polkadot/pull/6050) Low - Add fast-unstsake pallet to all runtimes
* [S] ⏳ pending non-critical audit [#12277](https://github.com/paritytech/substrate/pull/12277) Low - Add storage size component to weights

Proposal hash: `0xf1eeaa09f9a85633cf7f1fa588bf3247a58acf9f4cb3e8e12350833c595bc7d3`

You can review the hash and changes in the release notes and use SRTool to verify proposal hash - make sure to vote at your convenience! This proposal is submitted as an **external motion**: meaning after Council vote, the community will need to vote on the proposal in referenda queue. 

- This content is about a new plan to fix a previous issue with a project called Referendum 74.
- The first plan didn't work, so they made changes to improve it.
- Instead of combining actions into one, they separated them into individual actions.
- It adds a new connection for something called Bifrost (ParaId 2030).
- They will transfer 22 DOT (a type of money) for these actions.
- They want to make this happen quickly since a similar plan was already approved.

**Note: Supersedes 282**

This is a fix of [Referendum 74](https://polkadot.polkassembly.io/referendum/74), which [failed to execute properly](https://matrix.to/#/!OwgojQyBzTlUQGGLhq:matrix.parity.io/$WokrZ22XOgT8nAIUmx18WYRUsF3a-F6xcezGReQZ58A?via=matrix.parity.io&via=corepaper.org&via=matrix.org). Instead of using a Transact instruction containing a batch call, this uses a batch of Transact instructions, each with one call in it. This should work on the current version of Polkadot.

In addition to the original 5 channel requests, this also adds a sixth pair with ParaId 2030 (Bifrost).

The force_transfer is for 22 DOT: 20 for the sixth parachain (the 100 DOT from Ref 74 did get transferred) and 2 DOT for the XCM execution fees (the remainder of which will be transferred back to the Treasury).

Since the referendum already passed, requesting TC to fast track this one, presuming it passes Council.

Statemint HRMP Channel Establishment

- A new proposal wants to add a special group called a "common good parachain" to Polkadot, which will help collectives.
- The first group will probably be called the Polkadot Alliance.
- This parachain will help other groups in the Polkadot network too.
- There won't be a similar group for Kusama, but Kusama may join some collectives.
- There will be votes to approve the creation and use of the parachain.
- The first steps include registering the parachain and allowing it to start working.
- More details will come when the official plans are released.

As outlined in a [recent blog post](https://polkadot.network/blog/proposal-for-common-good-parachains/), this discussion is about a proposal to add a new common good parachain to Polkadot focused on collectives. The first collective to form will likely be the [Polkadot Alliance](https://docs.google.com/document/d/1aXlVDDQj6v8kOTvbMXBmenBZ3Sfn5zZf0ipQbYvdipo/edit#), but this parachain will also support other collectives that are in service of the Polkadot network.

There are no plans for a Kusama counterpart to the Polkadot Collectives parachain. In fact, the Kusama network itself may join several collectives to exercise its voice within the Polkadot ecosystem. For example, the Kusama network could join the Polkadot Alliance to set the standards for Polkadot brand use.

Other collectives do not warrant two distinct groups, like the [Technical Fellowship](https://forum.polkadot.network/t/calling-polkadot-core-developers/506). This group of technical experts who have made core protocol contributions to the network, would have nearly identical member sets, as the developers most intimatly familiar with Polkadot's inner workings deploy most of their code on Kusama as a step toward Polkadot.

I intend to submit this proposal to the Council to register and onboard the Collectives parachain with a four-year lease, and posting here first to open discussion.

The full launch will include a series of referenda on Polkadot for approval by the entire stakeholder body. These will be roughly as follows:

1. This proposal, to register the parachain and set the lease period. Once on board, it should start producing blocks. However, since it is not a trusted teleporter from the Relay Chain's point of view, nobody will be able to transact on it as there won't be any DOT with which to pay fees.
1. Runtime upgrade to the Relay Chain to include Collectives as a trusted teleporter.

Finally, I would expect a referendum to initiate the Alliance, which could come before or after the Relay Chain's recognition of the parachain as a teleporter. However, this is outside the scope of this discussion; I expect the Alliance founders to propose how they would like to launch.

The call details will be finalized when Parity publishes the [Collectives genesis release](https://github.com/paritytech/cumulus/releases/tag/parachains-collectives-v9290) and the Technical Committee indicates a rough enactment timeframe, which is needed to set the first period of the lease. The call will be a batch with `registrar.force_register` and `slots.force_lease` and the appropriate parameters.

--------

EDIT: Including call info.

Call hash: `0x9ef867bcaaee9750487738c6e6537eb52a3047c7bb2f06eb30dc05073dae90d5`

For some reason Polkassembly won't allow me to add the entire Polkadot JS link for the call (guessing it is too large), but it is as follows:

![](https://i.imgur.com/DDU8FPX.png)

Polkadot Collectives Common Good Parachain Proposal

- Tether has registered a new token called USDT on Polkadot's Statemint platform.
- They want Polkadot governance to make USDT able to pay transaction fees without needing DOT tokens.
- There are two types of assets on Statemint: Sufficient (which can be used freely) and Non-Sufficient (which need DOT to exist).
- If USDT is approved as Sufficient, users won't have to hold DOT to create accounts.
- This change would help USDT users have more flexibility on Polkadot Network.
- The stablecoin can support various transactions and boost the ecosystem, especially for decentralized finance (DeFi).
- Tether and Polkadot both announced this proposal through their official channels.

[Tether](https://tether.to/en/) registered USDT on Statemint (asset ID `1984` - it can be verified here). The team is requesting Polkadot governance to make it sufficient such that it can pay transaction fees and exist on accounts without DOT. Tether's announcement can be found [HERE](https://tether.to/en/tether-tokens-usdt-live-on-polkadot/). Polkadot's announcement can be found [HERE](https://twitter.com/Polkadot/status/1573299786266050561).

On Statemint, assets can be Sufficient or Non-Sufficient. To hold a Non-Sufficient asset, the Statemint account needs to exist on-chain. This is different from Ethereum where a non-existent account can hold ERC-20 tokens, as users need to ensure that the receiver account has at least 0.1 DOT which is the Existential Deposit for a Statemint account. However, if an asset is Sufficient, the Existential Deposit in DOT on the receiver account is not needed to create the account; the asset itself is sufficient. The team is requesting this property to be voted by governance.

This proposal would allow much more flexibility for holders on Polkadot Network and the stablecoin will power transactions on Polkadot’s Statemint needed for asset deployment and balance-keeping of fungible and non-fungible tokens flowing across the web of blockchains. Many in the community believe as well that a stablecoin like USDT can boost the ecosystem and support an increase of transactions, specifically on DeFi-focused chains.

**Call on Statemint**

- Encoded call: `0x3212011f00d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d282b92a000100`

- Call hash: `0x842d8a934c2aa86a909e0232f730d2f974bfc01e307703a07eefbad6efdb9e1d`

![](https://i.ibb.co/smBWXHt/Screenshot-2022-09-26-at-09-23-00.png)

**Call on Relay Chain**

- Call hash: `0x5eea32679cdac9fc69d2d1ff7740104ec2bb6d412cb121505dbece9d34a239fd`

- Call data: `0x630001000100a10f0204060202286bee39023212011f00d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d200d8e5d105e214d8c57e5819fb6d820883f44a617a78a7a6237cb9627ec73a26d282b92a000100`

![](https://i.ibb.co/XLwTgc6/Screenshot-2022-09-26-at-09-24-29.png)



Proposal for USDT Token Sufficiency on Statemint

- The proposal plans to update Polkadot's and Statemint's systems to new versions, v9291 and v9290.
- It includes several improvements and fixes for Polkadot, like making some types public and fixing rewards.
- Statemint will also get updates to help with performance and prepare for new features.
- The proposal is submitted for review and must be approved by the Council and then voted on by the community.
- There are specific tasks listed in the proposal, which have different priority levels (low, medium).
- Users can vote on the proposal when it’s time.

This proposal aims to upgrade both Polkadot’s and Statemint’s runtimes to [v9291](https://github.com/paritytech/polkadot/releases/tag/v0.9.29) and [v9290](https://github.com/paritytech/cumulus/releases/tag/parachains-v9290) respectively. For this, the proposal includes a batch call including both runtime upgrade proposals. 

### On Polkadot

This upgrade fixes issues and includes:

**Runtime**

⏳ pending non-critical audit #11813 Low - Proposal: flatten allpallets and similar types

✅ trivial #12032 Low - Contracts: make chain extension state types public

✅ trivial #11670 Low - Replace t::accountid with <t::lookup as staticlookup>::source

✅ trivial #12059 Low - Revert "auto-incremental collectionid"

✅ trivial #12095 ❗️ Medium - Fix nomination pools pending rewards rpc

#12138 Low - Weight v1.5: opaque struct

✅ audited #12145 Low - Uniques: reset approved account after transfer

✅ trivial #12136 Low - Emit events for inter contract calls

✅ audited #12154 Low - [fix] make sure pool metadata is removed on pool dissolve

Proposal hash: `0x8fe3a4b4214f090c01c1da47882c41eb08e0544d379c7e1959dcdc4810e12c50`

### On Statemint: 

[C] #1454 Low - [feature] add xcm benchmark weights to statemint

[C] #1551 Low - Update cumulus to latest substrate and polkadot master

Among other things, it includes an update to the XCM weight calculations and prepares for the first Collectives parachain.

- Proposal hash: `0x076ee423671cc95bd1eb19675009154d4e6b817554d755e6627c6138094a924b` 

- Authorize Upgrade call: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fstatemint-rpc.polkadot.io#/extrinsics/decode/0x01025256522299bfb951fa5726858cbe87df3ad0794352087430a23727849d3ebc20)

![](https://i.ibb.co/C1T25Wd/Screenshot-2022-10-06-at-16-28-02.png)

Please note this is submitted as an external motion: meaning if/after Council approves, this will also be up for vote by the community to decide on the upgrades. 

### Complete batch call:

![](https://i.ibb.co/vmKqGxG/Screenshot-2022-10-06-at-18-01-57.png)

Proposal hash: `0xbc2cb73740d701dac3fa5f31b7b23e552d6160ccd40d95746e91c131c699523d`

Make sure to vote at your convenience!


Runtime Upgrade v9291 on Polkadot + v9290 on Statemint

- Polkadot is launching new nomination pools for DOT-holders to make staking easier.
- You can join a pool with just 1 DOT, making it accessible for more people.
- Creating a pool will require 200 DOTs as initial collateral, which can earn rewards.
- There will be a limit of 64 pools and 16,000 members in total, but these limits can be increased later if needed.
- The proposal aims to ensure that Pools can scale up as needed.
- The community will vote to decide if this proposal is approved after council approval.

Polkadot community, the time has finally come:

Nomination pools can go live any time now in Polkadot. This is a great milestone, removing any barrier for native relay chain staking for DOT-holders. This proposal suggests the following configuration for nomination pools on Polkadot, following Kian's advice from the staking team:

**1 DOT to join a pool.** "I actually used to suggest 5 DOTs for a slightly higher sybil resistance, but I think the 5x factor here is not that big of a difference, and allowing staker holders to join pools with at little as 1 DOT is a nice milestone. Moreover, this sybil attack is not really viable as we can easily lift the limit on maximum members (mentioned below) and then it would have no effect."

**200 DOTs to create a pool.** "This is not a cost or deposit. It is actually the initial collateral/stake of the pool, and by setting it to 200, it will ensure that all pools have an initial stake that’s more than the minimum that’s needed to earn rewards (~170 as of now). This initial stake still earns rewards for the creator of the pool, and can be unstaked once the pool is being dissolved."

**Maximum of 64 pools and 16k members in all pools**. "These are only there so that if there is a bug, we can easily migrate the data and perform a fix. If we reach these limits, they can trivially be lifted to a higher value. Moreover, if pools work fine for e.g. ~6 months, we can proceed with lifting them altogether."

"I have worked hard on communicating that: “Pools are designed to be infinitely scalable”, I am suggesting these limits only out of extra caution."

This initial configuration composition, aiming to be presented for a vote if the community agrees, can be found [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x270a0100e40b540200000000000000000000000100204aa9d101000000000000000000000140000000010040000000). Preimage is submitted. Please note this is an external motion needing root origin: after Council approval, the community will vote to approve or reject this proposal in referenda queue. 

Polkadot Nomination Pools Initial Configuration

- The proposal is about funding a project called Gossamer.
- Gossamer helps build and run nodes for different blockchains using a programming language called Go.
- It is designed for the Polkadot ecosystem, which is a system of interconnected blockchains.
- The project will take 12 months to complete after getting support from the Web3 Foundation Grants Program.
- The goal is to make the Polkadot ecosystem have different types of clients.
- The proposal needs to be approved and then voted on by the community.
- More details about the budget and plans are available in the post.

The proposal aims to cover the costs for further development of **Gossamer**: a Polkadot host written in Go - a framework to build and run nodes for different blockchain protocols compatible with the Polkadot ecosystem. The timeline of the proposal is 12 months, after the successful collaboration with the Web3 Foundation Grants Program on the initial steps of this development. 

The overall goal is for Gossamer is **to provide the functionality needed to bring true client diversity to the Polkadot ecosystem** Budget, milestones and overall roadmap can be found on [the post](https://polkadot.polkassembly.io/motion/267). Please note that this is up for vote as an external motion: after/if the Council approves, this will be up for vote by the community. Make sure to review and vote at your convenience!

Original Treasury post: [https://polkadot.polkassembly.io/treasury/168](https://polkadot.polkassembly.io/treasury/168)

Original discussion post: [https://polkadot.polkassembly.io/post/1260](https://polkadot.polkassembly.io/post/1260)

External Motion: #168 Gossamer Ongoing Development Grant

- Polkadot has a new plan to improve its software, called the runtime.
- This new version is called v9281 and fixes a security problem found in the last version.
- The issue allowed fake information to be added to blocks, which is very important to fix.
- The update includes many changes that make Polkadot work better and safer.
- It has been checked and approved by experts to ensure everything is secure.
- The community will vote on whether to accept these changes.
- If approved, they will be added to Polkadot for everyone to use.

The proposal aims to upgrade Polkadot's runtime to [v9281](https://github.com/paritytech/polkadot/releases/tag/v0.9.28) after an [issue was identified](https://forum.polkadot.network/t/security-vulnerability-executing-unauthorized-xcm-messages/553) on the last release presenting the possibility of adding inherents containing fake data to a block. This release fixes the vulnerabilities and includes: 

**Runtime**

✅ audited #11918 Low - Make new storage layer truly default

✅ trivial #11690 Low - Add event to pallet asset-tx-payment

✅ audited #11796 Low - Auto-incremental collectionid

✅ trivial #11985 Low - Pallet-contracts: fix 16bit func_id

✅ trivial #11991 Low - Contracts: apply depth limit when decoding

⏳ pending non-critical audit #11819 ❗️ Medium - Transaction payment runtime api: query call info and fee details

✅ audited #11927 Low - Transactional: wrap pallet::calls directly in storage layers

✅ trivial #5582 Low - Add nomination pools to polkadot runtime

✅ trivial #5910 Low - Update weights

It also includes the fix to a vulnerability which potentially impacts block authoring. If passed by the Council, this proposal should be voted by the community for final decision and enacted after. Make sure to vote at your convenience! Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.28). 

Proposal hash: `0xe9a09ca478bb39406f131a5fd4dab46edbf75d9ae3a9950eb0a74094943be4be`

Runtime v9281 Upgrade On Polkadot

- A proposal wants to upgrade the Polkadot Runtime to version v9280.
- The upgrade includes changes and new features that can be found online.
- One important change is the addition of nomination pools.
- These nomination pools will need to be set up through governance.
- Several other low and medium priority updates are also included in the proposal.
- If the Council approves it, the community will get to vote on it.
- Everyone is encouraged to participate in the voting process.

The proposal proposes an upgrade of the Polkadot Runtime to **v9280** - Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.28). Feel free to use srtool yourself to check the proposal hash. Among other changes, this release most notably **adds nomination pools to the Polkadot runtime** - please note that these will need to be configured via governance after enactment of this runtime upgrade. 

**Runtime**

✅ audited #11918 Low - Make new storage layer truly default

✅ trivial #11690 Low - Add event to pallet asset-tx-payment

✅ audited #11796 Low - Auto-incremental collectionid

✅ trivial #11985 Low - Pallet-contracts: fix 16bit func_id

✅ trivial #11991 Low - Contracts: apply depth limit when decoding

⏳ pending non-critical audit #11819 ❗️ Medium - Transaction payment runtime api: query call info and fee details

✅ audited #11927 Low - Transactional: wrap pallet::calls directly in storage layers

✅ trivial #5582 Low - Add nomination pools to polkadot runtime

✅ trivial #5910 Low - Update weights

If passed by the Council, this proposal should be voted by the community for final decision and enacted after. Make sure to vote at your convenience!

Polkadot Runtime Upgrade to v0.9.28

- A new motion corrects mistakes from previous proposals related to channel requests between Statemint and parachains.
- Five parachains (2021, 2031, 2032, 2035, 2046) want to connect with Statemint.
- The motion accepts these requests and opens return channels.
- Important treasury addresses and account IDs are provided for reference.
- The proposal requires a vote from the Council and then the community.
- It includes specific encoded call data needed for execution.
- The call hash for this proposal is `0xfa5da8a4d9ef08dd22dfbc189861cbb9275dc8c52e4ce9b04f21cc830b3d5617`.

Please note this motion replaces [motion 256](https://polkadot.polkassembly.io/motion/256) due to an error on the proposal weight and [motion 257](https://polkadot.polkassembly.io/motion/257) due to an error downgrading the call from the relay chain to native: the proposal fixes both mistakes.

Five more parachains have requested an HRMP channel with Statemint. This motion accepts them all and opens return channels.

**Handy Info**

- **Treasury Address**: `13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB`
- **Treasury AccountId:** `0x6d6f646c70792f74727372790000000000000000000000000000000000000000`
- **Statemint Address:** `13YMK2edbuhwMBxeUWm9c643A2wyYHwSVh1bCM7tShtg7Dtk`
- **Statemint AccountId:** `0x70617261e8030000000000000000000000000000000000000000000000000000`

- **Parachains that aim to open channels**: 2021, 2031, 2032, 2035, 2046.

**Call Construction**

These are constructed backwards. That is, the call to use as the proposal is at the end.

**Relay Chain Call to Execute**

First, we need the call that Statemint will execute on the Relay Chain. This accepts all channel requests and returns channel requests to the initiators.

- Encoded Call Data (Polkadot): 

```
0x1a02283c01e50700003c01ef0700003c01f00700003c01f30700003c01fe0700003c00e5070000e8030000009001003c00ef070000e8030000009001003c00f0070000e8030000009001003c00f3070000e8030000009001003c00fe070000e803000000900100
```

**Message from Statemint**

The above message needs to come from Statemint. So we put it into an XCM (the “Transact” instruction) along with purchasing some execution capacity and returning any leftover fees to the Treasury.

- Encoded Call Data (Statemint): 

```
0x1f0001010002140004000000000700c817a80413000000000700c817a80400060002286bee9d011a02283c01e50700003c01ef0700003c01f00700003c01f30700003c01fe0700003c00e5070000e8030000009001003c00ef070000e8030000009001003c00f0070000e8030000009001003c00f3070000e8030000009001003c00fe070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000
```

**Proposal on the Relay Chain**

But, governance is on the Relay Chain, not Statemint. So take some DOT from the Treasury (100 DOT for 10 channels at 10 DOT each plus 2 DOT for fees) and send a message to Statemint telling it to send a message back. This is the proposal to vote on.

- Encoded Call Data (Polkadot): 

``` 
0x1a02080502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d8bc7ced630001000100a10f0204060202286beef5021f0001010002140004000000000700c817a80413000000000700c817a8040006000700e40b54029d011a04283c01e50700003c01ef0700003c01f00700003c01f30700003c01fe0700003c00e5070000e8030000009001003c00ef070000e8030000009001003c00f0070000e8030000009001003c00f3070000e8030000009001003c00fe070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000
```

- Call Hash: `0xfa5da8a4d9ef08dd22dfbc189861cbb9275dc8c52e4ce9b04f21cc830b3d5617`

Preimage has already been submitted for verification by the community as well. After/if Council votes and passes this proposal, this will need to be voted by the community in referenda queue. 

Second Batch Of Statemint HRMP Channels (replacing motions 256 and 257)

- The v9270 runtime is used by Polkadot and Kusama.
- It allows buying and selling NFTs, which are special digital items.
- This change was added to something called the Uniques pallet.
- Statemine can now use certain assets to pay for XCM fees.
- Statemine will get this feature first, before Statemint. 
- Statemint does not have enough assets for this change yet.
- Not having the feature on Statemint does not affect how it works right now.

The [v9270 runtime](https://github.com/paritytech/cumulus/releases/tag/parachains-v9270) is based on the same release as the Polkadot/Kusama v9270 runtimes. For both Statemint and Statemine, this release introduces the ability to buy and sell NFTs in the Uniques pallet, introduced in [this PR](https://github.com/paritytech/substrate/pull/11398). For Statemine only, this release also allows the use of sufficient assets to pay [XCM fees](https://github.com/paritytech/cumulus/pull/1278). This feature will run on Statemine before making its way to Statemint; Statemint does not have any assets deemed sufficient yet, so not having it there will not affect current interactions.

Upgrade Statemint to v9270

- This proposal is about updating the Polkadot Runtime to a new version called v9270.
- The new version has release notes and changes that can be checked online.
- A special code called a proposal hash (0x55507b53f5c37e97e3faf9a9274dba0c5eace970aa5c653c179126f679ed496e) is included.
- If the Council approves the proposal, the Polkadot community can vote on it.
- Voting is important, and everyone is encouraged to participate when they can.

This proposal aims to upgrade the Polkadot Runtime to [v9270](https://github.com/paritytech/polkadot/releases/tag/v0.9.27) - Release notes, runtime changes, and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.27). Feel free to use srtool yourself to check the proposal hash.

Proposal hash: `0x55507b53f5c37e97e3faf9a9274dba0c5eace970aa5c653c179126f679ed496e`

If passed by the Council, this proposal should be voted by the Polkadot community and enacted after. Make sure to vote at your convenience!

Polkadot Runtime Upgrade to v9270

- A proposal is being made to upgrade Polkadot to version 9260.
- The upgrade includes changes to voting and sets new weights.
- The Council will be able to send messages (XCMs) with this upgrade.
- The proposal needs to be approved by the Council first.
- After Council approval, the Polkadot community will vote on it.
- Voting is important, so make sure to participate! 
- The unique code for this proposal is `0x282b1166e009892d0088efb1d7158b1c04f03394b9d9cff05e19eec76ecb4e7c`.

The motion proposes an upgrade of the Polkadot Runtime to **v9260** - Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.26). Feel free to use srtool yourself to check the proposal hash. On the runtime side, this upgrade executes some changes on referenda and conviction voting, update weights, allows Council to send XCMs, among other things.

If passed by the Council, this proposal should be voted by the Polkadot community and enacted after. Make sure to vote at your convenience!

Proposal hash: `0x282b1166e009892d0088efb1d7158b1c04f03394b9d9cff05e19eec76ecb4e7c`

Polkadot Runtime Upgrade to v9260

Discussion: https://polkadot.polkassembly.io/post/1158 This proposal aims to increase the maximum number of HRMP channels from 10 to 30. Note that number of inbound and outbound channels are separate configuration and therefore this is a batch call to update both values.

Increase maximum number of HRMP channels from 10 to 30

- A new proposal is up for voting to upgrade Polkadot's system to version v0.9.25.
- You can find details about the upgrade, including changes and release notes, online.
- The community needs to vote on this proposal after the Council decides on it.
- The unique code for this proposal is 0x73a9fe9a8dcced92ad7eb36963f64d7b49a4f66a2c5e626a812e5b6cd0e56d42.
- Everyone is encouraged to participate and vote when they can.

The proposal to upgrade Polkadot's runtime to [v9250](https://github.com/paritytech/polkadot/releases/tag/v0.9.25) is now up for vote!

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.25). Feel free to use srtool yourself to check the proposal hash. If passed by the Council, this proposal should be voted by the community and enacted after. 

Make sure to vote at your convenience!

Proposal hash: `0x73a9fe9a8dcced92ad7eb36963f64d7b49a4f66a2c5e626a812e5b6cd0e56d42`

Runtime Upgrade 0.9.25

- The v9230 runtime is a new version made for Polkadot and Kusama.
- It includes some important changes from the previous version, v9190.
- The names of certain parts in the Uniques pallet have changed from "classes" and "instances" to "collections" and "items."
- This change helps to match what is commonly used in the industry.
- NFT collection owners can now decide how many items are in their collection.
- To create new types of assets, it now costs 10 DOT.

The [v9230 runtime](https://github.com/paritytech/cumulus/releases/tag/release-parachains-v9230) is based on the same release as the Polkadot/Kusama v9230 runtimes. Besides the XCM and core Substrate changes that happened between v9190 (off which the current v900 was based), v9230 most notably includes a renaming of `class`es and `instance`s to [`collection`s and `item`s](https://github.com/paritytech/substrate/pull/11389) in the Uniques pallet to be more aligned with industry standards. It also allows NFT collection owners to set a [max number of items](https://github.com/paritytech/substrate/pull/11441). Finally, this release updates the deposits required to create both fungible and non-fungible asset classes to 10 DOT.

Democracy External Proposals