- 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

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

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

- 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

- 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

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

- 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 Web3 Foundation and other teams joined the World Economic Forum (WEF) 2022 to talk about blockchain technology.
- They wanted to help important leaders learn about Polkadot and its uses.
- The goal was to build relationships with business leaders and journalists who don't usually know about Polkadot.
- They aimed to show how Polkadot can help businesses and improve real-life situations, not just finance.
- The foundation also wanted the media to understand blockchain and its impact on our lives.
- They believe teaching today's leaders will help create positive changes for the future.

Web3 Foundation, together with the parachain teams of PureStake (Moonbeam), Enjin (Efinity), BOTLabs GmbH (KILT), Trace Labs (OriginTrail), Robonomics, and Bit.country to participate in one of the most influential global events; the Annual Meeting of the World Economic Forum (WEF) 2022. In order to achieve real change for tomorrow, we need to educate the leaders of today, many of whom attend the WEF: this presents a unique opportunity to build brand awareness and interest for Polkadot, build connections with enterprise audiences, business, tech, and mainstream media groups so that they better understand blockchain technology, take part in the Web3 roadmap and see Polkadot as the best technology platform for building blockchain projects.
The goals of this proposal are:

- to build Polkadot awareness among policymakers, business executives and CEOs, top-tier journalists and technologists, as these people are usually not part of our audience

- to create interest and establish strong relationships with them

- to present Polkadot products/networks/platforms/solutions

- to show the business audience how they could benefit from Polkadot products/networks/platforms/solutions and how Polkadot is already applicable in real-life cases, beyond DeFi

- to make the media audience understand blockchain technology and Polkadot and how blockchain can impact the way we live and do business

- to educate the leaders of today in order to deliver real change for tomorrow.

Further information on the proposal, including milestones, budget, agenda, participants and more can be found on [THIS LINK](https://docs.google.com/document/d/1GvXdn0mH4cOYTNYhWId3WA-a_SieSFupR4IIe71BC4M/edit)! 

Furthermore, discover Polkadot and Join the Web3 Movement at Davos on [THIS LINK](https://wef22.polkadot.network/).

**Treasury Payment Conditions:**

- Rate of CHF/USD calculation based on [Swiss National Bank foreign exchange rate](https://www.snb.ch/en/iabout/stat/statrep/id/current_interest_exchange_rates#t3). 
- Rate of USD/DOT calculation based on [EMA30 by Subscan on 19.05.2022](https://polkadot.subscan.io/tools/charts?type=price).


 Proposal: Polkadot at Davos during the World Economic Forum’s Annual Meeting 2022

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

Statemint: Upgrade to v9230

- There is a proposal to upgrade Polkadot to version 0.9.23.
- The new version has some changes, including updates on weights.
- You can find more details in the release notes.
- The Council needs to approve the proposal first.
- After approval, the community will vote on it.
- Everyone is encouraged to vote when they can.
- A special code, called a call hash, is used for the upgrade.

This proposal aims to upgrade Polkadot runtime to version [0.9.23](https://github.com/paritytech/polkadot/releases/tag/v0.9.23): 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.23). New changes on the runtime include an update on weights among other things. 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!

- Call hash for Polkadot upgrade: `0xa9d8065067376bb10ebf4c5d4933fb6d94c0edb3a5d477cf669e350d49558fda`

Polkadot Runtime Upgrade to v9230

This is a fix for referendum 62, which passed but failed to execute properly. Details of the problem and how to fix are in this [HackMd](https://hackmd.io/qAT35jE2Sn6IjBXlMXfuBg?view).

Fix: Establish HRMP Channels for Statemint

- A proposal is being made to upgrade Polkadot to a new version called 0.9.22.
- Information about this upgrade, including changes and important links, is available online.
- After the Council approves the proposal, the community will get to vote on it.
- Everyone is encouraged to vote when they can.
- A special code called a call hash for this upgrade is provided.

This proposal aims to upgrade Polkadot runtime to version [0.9.22](https://github.com/paritytech/polkadot/releases/tag/v0.9.22): 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.22). 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!

- Call hash for Polkadot upgrade: `0x061f7d9c2994b388cf69da9c4bef9f8c1ea1b00a66c43531f515aeacbe0a76a8`

Polkadot Runtime Upgrade to v9220

Five parachains have requested a channel with Statemint. This motion accepts all requests and opens return channels. Here are some important details:

1. Treasury Address: 13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB
2. Statemint Address: 13YMK2edbuhwMBxeUWm9c643A2wyYHwSVh1bCM7tShtg7Dtk
3. Parachains that want channels: 2011, 2000, 2004, 2006, 2012
4. Channel settings: maxCapacity is 1,000 and maxTotalSize is 102,400
5. HRMP settings: hrmpSenderDeposit and hrmpRecipientDeposit are both 100,000,000,000

The proposal involves taking some DOT from the Treasury and sending a message to Statemint. The encoded call data and call hash are provided for the Relay Chain Call to Execute.

So far, five parachains have requested an HRMP channel with Statemint. This motion accepts them all and opens return channels. ## Opening Notes ### Handy Info - Treasury Address: \`13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB\` - Treasury \`AccountId\`: \`0x6d6f646c70792f74727372790000000000000000000000000000000000000000\` - Statemint Address: \`13YMK2edbuhwMBxeUWm9c643A2wyYHwSVh1bCM7tShtg7Dtk\` - Statemint \`AccountId\`: \`0x70617261e8030000000000000000000000000000000000000000000000000000\` ### Parachains that want channels - 2011 - 2000 - 2004 - 2006 - 2012 ### Channel Config - \`maxCapacity: 1,000\` - \`maxTotalSize: 102,400\` ### HRMP Config - \`hrmpSenderDeposit: 100,000,000,000\` - \`hrmpRecipientDeposit: 100,000,000,000\` ## 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. !\[\](https://i.imgur.com/azd1Ygm.png) !\[\](https://i.imgur.com/zWItDfE.png) Encoded Call Data: \`\`\` 0x1a02283c01db0700003c01d00700003c01d40700003c01d60700003c01dc0700003c00db070000e8030000009001003c00d0070000e8030000009001003c00d4070000e8030000009001003c00d6070000e8030000009001003c00dc070000e803000000900100 \`\`\` ### 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. !\[\](https://i.imgur.com/i3SHuZV.png) !\[\](https://i.imgur.com/eXXtCrw.png) Encoded Call Data: \`\`\` 0x1f0001010002140004000000000700c817a80413000000000700c817a80400060002286bee9d011a02283c01db0700003c01d00700003c01d40700003c01d60700003c01dc0700003c00db070000e8030000009001003c00d0070000e8030000009001003c00d4070000e8030000009001003c00d6070000e8030000009001003c00dc070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000 \`\`\` ### 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. !\[\](https://i.imgur.com/WvVLRuK.png) Encoded Call Data: \`\`\` 0x1a02080502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d8bc7ced630001000100a10f0204060202286beeed021f0001010002140004000000000700c817a80413000000000700c817a80400060002286bee9d011a02283c01db0700003c01d00700003c01d40700003c01d60700003c01dc0700003c00db070000e8030000009001003c00d0070000e8030000009001003c00d4070000e8030000009001003c00d6070000e8030000009001003c00dc070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000 \`\`\` Call Hash: \`\`\` 0x6306b068f6a71eb1db5abd9609a0ffbbe7c441c9144ecf8a49e7c2bc19f7f6e9 \`\`\` ## Appendix: Relevant Storage Items \*\*\`configuration.activeConfig: PolkadotRuntimeParachainsConfigurationHostConfiguration\`\*\* \`\`\`json= { maxCodeSize: 10,485,760 maxHeadDataSize: 20,480 maxUpwardQueueCount: 10 maxUpwardQueueSize: 51,200 maxUpwardMessageSize: 51,200 maxUpwardMessageNumPerCandidate: 10 hrmpMaxMessageNumPerCandidate: 10 validationUpgradeCooldown: 14,400 validationUpgradeDelay: 600 maxPovSize: 5,242,880 maxDownwardMessageSize: 51,200 umpServiceTotalWeight: 100,000,000,000 hrmpMaxParachainOutboundChannels: 10 hrmpMaxParathreadOutboundChannels: 0 hrmpSenderDeposit: 100,000,000,000 hrmpRecipientDeposit: 100,000,000,000 hrmpChannelMaxCapacity: 1,000 hrmpChannelMaxTotalSize: 102,400 hrmpMaxParachainInboundChannels: 10 hrmpMaxParathreadInboundChannels: 0 hrmpChannelMaxMessageSize: 102,400 codeRetentionPeriod: 14,400 parathreadCores: 0 parathreadRetries: 0 groupRotationFrequency: 10 chainAvailabilityPeriod: 10 threadAvailabilityPeriod: 10 schedulingLookahead: 1 maxValidatorsPerCore: 5 maxValidators: 200 disputePeriod: 6 disputePostConclusionAcceptancePeriod: 600 disputeMaxSpamSlots: 2 disputeConclusionByTimeOutPeriod: 600 noShowSlots: 2 nDelayTranches: 89 zerothDelayTrancheWidth: 0 neededApprovals: 30 relayVrfModuloSamples: 40 umpMaxIndividualWeight: 20,000,000,000 pvfCheckingEnabled: false pvfVotingTtl: 2 minimumValidationUpgradeDelay: 20 } \`\`\` \*\*\`hrmp.hrmpOpenChannelRequests: Option\`\*\* \`\`\`json \[ \[ \[ { sender: 2,011 recipient: 1,000 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \[ \[ { sender: 2,000 recipient: 2,035 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \[ \[ { sender: 2,000 recipient: 2,034 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \[ \[ { sender: 2,000 recipient: 2,032 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \[ \[ { sender: 2,012 recipient: 2,000 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \[ \[ { sender: 2,000 recipient: 1,000 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \[ \[ { sender: 2,004 recipient: 1,000 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \[ \[ { sender: 2,006 recipient: 1,000 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \[ \[ { sender: 2,012 recipient: 1,000 } \] { confirmed: false age: 0 senderDeposit: 100,000,000,000 maxMessageSize: 102,400 maxCapacity: 1,000 maxTotalSize: 102,400 } \] \] \`\`\`

First Statemint HRMP Channels

- A new upgrade for Polkadot is proposed to change its version to 0.9.20.
- Important information about this upgrade can be found in the release notes.
- The upgrade includes improvements for faster parachain block times.
- There’s a special code (hash) for this proposal.
- If the Council approves, the community will get to vote on it.
- Everyone is encouraged to vote when they can!

This proposal aims to upgrade Polkadot runtime to version [0.9.20](https://github.com/paritytech/polkadot/releases/tag/v0.9.20): 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.20). On the runtime side, you can check the changes in the link above. Other improvements on the client side for this release include a PR [aiming to reduce bandwidth](https://github.com/paritytech/polkadot/pull/5164) to improve parachain block times, in response to [the issues described on this post](https://kusama.polkassembly.io/post/1424)  

- Call hash for Polkadot upgrade: `0xf94667fb9411092c1c0b2f157021ff871d92c60becfe8cd467a16e6d6ccf4a92`

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!

Polkadot Runtime Upgrade to v9200

In light of discussion in Polkadot Direction, I've added a competing motion to the [1,000 DOT proposal](https://polkadot.polkassembly.io/motion/192) with a 10 DOT proposal.

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

Lower HRMP Channel Deposits to 10 DOT

- Phala parachain is currently stuck or "bricked."
- The team wants to fix this by asking for help with a special call to change its code.
- Phala Network became a parachain recently.
- They found a mistake in their setup that prevents upgrades.
- Both sudo and democracy are turned off, making it hard to add new features.
- Without help, the parachain will stay stuck forever.
- More details about the issue and their plans are available in a discussion link.

TL;DR. Phala parachain is bricked. The team is requesting a Motion to fast-track a `Paras.forceSetCurrentCode` call to unbrick the parachain.
_______________
Phala Network (id: 2035) became a parachain recently. However, during the progressive launching process, the team noticed that there's no way to upgrade the runtime due to the misconfiguration in the genesis runtime. Specifically, the genesis runtime has both sudo and democracy disabled. Without the help from the relaychain side, the parachain will be "bricked" forever -- all the functions need to be enabled by runtime upgrades which is infeasible due to the problem.

Proposal hash: `0x7af427aa7665a073ca61b83c04791f185d9170ea2e49a8a7be323650cea8b75f`

More info on the misconfiguration of the runtime, force runtime update on relay chain and team's roadmap can be found in the discussion link: [https://polkadot.polkassembly.io/post/1005](https://polkadot.polkassembly.io/post/1005). Preimage is submitted by the team. 



Unbrick Phala Network Parachain (at team's request)

- This proposal is about upgrading Polkadot and Statemint.
- The Relay Chain will have a new version called 0.9.19, which includes helpful updates like child bounties and crowdloan migration.
- Users are encouraged to vote on the proposal after it is approved by the Council.
- Statemint will launch its version 900, which allows moving DOT (Polkadot's currency) easily between the Relay Chain and Statemint.
- With Statemint v900, users can also open channels and manage NFTs without any problems.

This proposal is for a batch that will upgrade both the Relay Chain and Statemint.

## Relay Chain

This proposal aims to upgrade Polkadot runtime to version [0.9.19](https://github.com/paritytech/polkadot/releases/tag/v0.9.19): 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.19). On the runtime side, this release includes, among others, child bounties, and a PR enabling migration of slot depositors in crowdloan migration for parachains to be able to swap slots, among other things. 

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!

## Statemint

Statemint v900 ([release notes](https://github.com/paritytech/cumulus/releases/tag/parachains-v9.0.0)) marks the true launch of Statemint and its functionality. With audits having been complete for several months, the only thing Statemint needed was a way to get DOT from the Polkadot Relay onto Statemint. With the enabling of disputes and XCM on the Relay Chain as of v9190, this is now possible. The v900 release allows users of Statemint to teleport DOT from the Relay Chain, teleport it back, open HRMP channels, and perform all asset/NFT operations without restrictions.

This Statemint release also includes some minor Uniques pallet improvements in preparation for XCM V3, which will allow users and applications to use NFTs over XCM.

## Call

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

![statemint auth](https://i.imgur.com/Wcmmg8m.png)

Polkadot Relay Chain v9190 and Statemint v900 Upgrades

The Statemint v800 runtime upgrade is relatively low impact, especially as teleports and asset creation are not enabled yet. However, this sets the stage for v900, in which I plan to propose lifting all restrictions on Statemint. The purpose of upgrading to v800 is to ensure that Statemint is on the same version as Westmint and Statemine such that testing the v900 w/r/t migrations is as similar as possible.

Statemint Upgrade v800

- The Composable Finance team had a problem on the Picasso chain in Kusama.
- There was a mistake in the weight calculations for something called "pallet-democracy."
- This mistake could cause the chain to stop working after a certain time.
- A public file for using the software can be found online.
- There is a design related to preimages shared with a picture.
- A preimage hash was also provided, which is a special type of code.
- The original message about this problem can be found in a post online.

The **Composable Finance** team has had [the same issue](https://kusama.polkassembly.io/motion/427) essentially as on Picasso chain on Kusama, so one particular cause: The team had a stray [todo!](https://github.com/ComposableFi/composable/blob/094d4668400c7832ccd601863a175eeb931782e3/runtime/picasso/src/weights/democracy.rs?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20main%2C%20%5Bdata-pjax-container%5D#L117) in the weight calculations for pallet-democracy [which doomed the chain to be bricked once the launch period elapses](https://github.com/paritytech/substrate/blob/542a8585339d2581e641df339d254d7dd22b1456/frame/democracy/src/lib.rs?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20main%2C%20%5Bdata-pjax-container%5D#L1758-L1763).

- Public wasm file to use can be found here: [https://github.com/ComposableFi/composable/releases/tag/v2.1.2](https://github.com/ComposableFi/composable/releases/tag/v2.1.2)

- **Preimage design**:

![](https://i.ibb.co/sjtNZqF/Screenshot-2022-03-28-at-09-53-06.png)

- **Preimage hash**: `0xad2813b46b52fe8f38cb5af7da9c7f0f66416900070b949daa62cf92bbdc6fd7`

(Please note that preimage has been already submitted).

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

Help Composable Finance Unbrick Their Chain

- The proposal is to upgrade Polkadot to version 0.9.18.
- Important changes include logging in two parachains, and adding new types for contracts.
- The upgrade will allow for the use of a special function called set_code.
- A specific call hash is mentioned for the upgrade.
- The Council will vote on the proposal, and then the community can vote as well.
- Everyone should remember to vote when it's their turn!

This proposal aims to upgrade Polkadot’s runtime to version [0.9.18](https://github.com/paritytech/polkadot/releases/tag/v0.9.18): 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.18). This release includes, among others, PR 4772 (login two parachains to swap slots), PR 10947 (bringing back maxnominators as a meatada constant), PR 4851 (adding proxy types for Kappa Sigma Mu) and PR 10690 (upgradable contracts using set_code function).

- Call hash for Polkadot upgrade: `0xa9ad07f0ea8e95c15247ba05a2754405acbf4de6cea8fe0cfdb94196c6093670`

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!

Runtime Upgrade v9180 - Polkadot Network

- A proposal suggested by Kian from the Staking team aims to change nomination limits in Polkadot.
- The goal is to increase the maximum number of nomination intentions from 22,500 to 50,000.
- It also suggests lowering the stake needed to submit a nomination intention to 10 DOT.
- This change is possible because of new features released in Polkadot's runtime 9170.
- The proposal should be acted upon before the number of nominators reaches 22,500 to avoid issues.
- There should be no negative impact on current stakers with this proposal.

This proposal is explained as suggested by Kian from the Staking team.

**NOTE**: this proposal is using the new terminology introduced in [the February newsletters](https://docs.google.com/document/d/1bisngPfte-P2vMuP_JrV6fIpNnd04uCWrqt4UbFklF8/edit#heading=h.kdyyexvr13fu), please refer to that for a recap.

This proposal aims to alter the limits on the nomination intention for Polkadot, namely lowering them since they are not strictly needed anymore.

As of release of runtime 9170, pallet-bags-list has been [fully enabled in Polkadot](https://docs.google.com/document/d/1bisngPfte-P2vMuP_JrV6fIpNnd04uCWrqt4UbFklF8/edit#heading=h.z30dvegsxvsi), and setting the intention to nominate should now be made possible for a larger audience. In essence, the number of intentions need no longer be bounded by 22,500. The bags-list will take care of picking up the top 22,500 nominations (those who become “electing”). Thus, we propose the following:

1. Increase the number of possible intentions to **50,000**. 

**NOTE**: that this number could be lifted altogether, but we suggest keeping an upper bound that’s dynamically controlled by the governance as an extra safety measure, at least for the time being.

2. Decrease the amount of stake needed to submit a nomination intention to **10 DOT**.

**NOTE**: Similarly, this number could also be lowered back to 1 DOTs, which is the existential deposit, but we suggest doing that as a next step within the next few months, and for now keep this small limit to prevent a massive sudden influx of intentions. 

Call design:

![](https://i.ibb.co/RczyGyY/Screenshot-2022-03-09-at-09-57-10.png)

Encoded call data: `0x071700e87648170000000000000000000000000000000000000000000000000000000150c3000001b0040000015a00000000`

**Urgency**: Ideally, this proposal should be enacted before the number of total nominators in Polkadot reaches 22,500 (the value for which at the time of this writing is 21,214). If it does, the ‘nominate’ transaction will become unavailable to all stakers. This proposal should have no negative effect on any stakers, as it will only relax the limits to submit for nomination intentions.

Link to discussion post: [HERE](https://polkadot.polkassembly.io/post/921). 

Democracy Referenda