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

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<PolkadotRuntimeParachainsHrmpHrmpOpenChannelRequest>`**

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

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

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

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)

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

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

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

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

Polkadot Proposal: Lowering Nomination Intention Limits

This is the proposal for crowdloan extensions discussed [here](https://polkadot.polkassembly.io/post/911). The included crowdloans were based on comments from the thread and confirmed with contacts from each team. Four teams either declined an extension or did not respond to the discussion.

- 2003: Darwinia
- 2008: Crust
- 2011: Equilibrium
- 2013: Litentry
- 2026: Nodle
- 2035: Phala
- 2038: Geminis

Extend Current LP7 Crowdloans

Please note this is a `batch` call proposal, combining the Polkadot upgrade with the Statemint upgrade: 

- Batch call hash: `0xbf60cbdd406036e0b6a3028763bfe20d9569780c0ffddc75cf209358fce3111c`
- Call design: [here](https://drive.google.com/file/d/1emtVtvZ-4skQnKDJj5r0_fP1bm-q4l4l/view?usp=sharing).

The **Polkadot runtime** will be upgraded to **v9170** - Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.17-rc4). This release improves the block time degradation issues, as seen [on Kusama](https://github.com/paritytech/polkadot/issues/4911). It also includes new changes in the runtime: like optimised weights and contains the PR to fully enable the bags list on polkadot, which **removes the need of having a strict maximum count for nominators** and also fully alleviates the phantom nominator issue. Both of these are explained further [in the January issue of "Polkadot Staking Progress”](https://docs.google.com/document/d/12MPnxGzoiRcJJYAGOYVU8dGUkqybuhoQX7wg5ouGfgU/edit?usp=sharing). 
- Call hash for polkadot upgrade: `0x8eb2806cbdf1a4ba91334669b2476870134db3af5c77f418152af0ad354d3b32`
 
The **Statemint runtime** will be upgraded to [v700](https://github.com/paritytech/cumulus/releases/tag/parachains-v7.0.0-rc8):

-  The Uniques pallet includes an [extra storage item](https://github.com/paritytech/substrate/pull/9940) linking class owners to their NFT classes. This storage map comes in handy for UI developers, especially around the UX of creating and minting NFTs.

- With the inclusion of [Polkadot 4470](https://github.com/paritytech/polkadot/pull/4470) and [Cumulus 831](https://github.com/paritytech/cumulus/pull/831), parachains that have HRMP channels with Statemint will finally be able to use them in both directions. For parachain developers, note that this is a breaking change and if you've used reserve backed transfers from Statemint then you will need to migrate some storage items.

- It addresses all issues found by independent auditors regarding the Statemint runtimes. For Statemint, this means that once teleportation is ready (pending some final disputes related features) it should be OK to lift the call filter restricting asset/unique creation, opening the door for fungible and non-fungible assets in the Polkadot network. 

As usual, the Statemint proposal will dispatch an `authorizeUpgrade` message. All info about the upgrade can be found on the link above. 

- Hash for XCM call (council motion) can be found [HERE](https://drive.google.com/file/d/1BvnGFDK2KVjvFNMxs6qA9evkeSyniOdS/view?usp=sharing).
 - Hash: `0x8adb4ccdf996f05fa7941ce3b56ecec6dd49a88d9db445963e813ac10cadd326`.
- Encoded call: `0x01028adb4ccdf996f05fa7941ce3b56ecec6dd49a88d9db445963e813ac10cadd326`
- Runtime release can be found [HERE](https://github.com/paritytech/cumulus/releases/tag/parachains-v7.0.0-rc8).

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 v9170 and Statemint Runtime Upgrade to v700

This new proposal aims to enact the same as [motion 157](https://polkadot.polkassembly.io/motion/157): to temporarily increase the nomination limit to `160` DOTs. This allows for the permissionless `chill_other` transaction to be used and prune the number of nominators, in order to keep the nomination ecosystem of Polkadot active, whilst we wait for the enactment of the next runtime upgrade on Polkadot.

The enacted proposal unfortunately contained a major flaw: the numerical values are not in DOTs, but rather in PLANKs, the smallest unit of the DOT currency. Thus, the correct value for minimum nominator bond should have been set to `160 * (10^10)`, i.e. `1600,000,000,000`.
 
All values are unchanged except for `minNominatorBond`.

The correct call hash and data:

- Call data: `0x071700806e877401000000000000000000000000000000000000000000000000000001e457000001b0040000015a`

- Call hash: `0xbdf1c925dbca9e1e55de029db3786ea71949ff872e5b53588f46d0db6ccae379`

Polkadot’s Update to 160 DOTs as minimum nomination limit: A follow-up proposal fixing a unit mistake

This is a short term upgrade proposed to increase the limit of DOTs for nomination from 120 DOTs to 160, maintaining the increase of 40 DOTs that the network has had throughout this period of updating the nominator limit through governance. The reason for this is the combination of the following:

- Polkadot’s [0.9.16](https://github.com/paritytech/polkadot/releases/tag/v0.9.16) upgrade was scheduled to contain a fix that would completely remove the 120 DOTs limit. This explained thoroughly in the monthly staking report of [January 2022](https://gist.github.com/kianenigma/aa835946455b9a3f167821b9d05ba376#january-2022). After the 0.9.16 update, the nomination limit would move to a dynamic system based on demand, rather than a fixed entry barrier.  
- Due to some unforeseen issues arisen after the deployment of 0.9.16 in Kusama, 0/9.16  has not yet been proposed to Polkadot.
- In the meantime, the number of nominators in Polkadot has been increased to reach the 22500 limit. 

As a consequence, we propose to temporarily increase the nomination limit to **160** DOTs. This allows for the permissionless `chill_other` transaction to be used and prune the number of nominators, in order to keep the nomination ecosystem of Polkadot active, whilst we wait for the enactment of runtime 0.9.16 on Polkadot.

 Proposal details: All values are unchanged except for `minNominatorBond`.

![](https://i.ibb.co/vz2vcdj/Screenshot-2022-02-21-at-18-31-17.png)

- Call hash: `0xb2286cbfdd18c265572d3305754b0dbe8ba1fd8da40ef48ff0d5ef40912f2291`

- Call data: `0x0717a00000000000000000000000000000000000000000000000000000000000000001e457000001b0040000015a`

Preimage is submitted. 

Polkadot’s Update to 160 DOTs as minimum nomination limit: The Reason

The proposal aims to upgrade Polkadot’s runtime to [v9151](https://github.com/paritytech/polkadot/releases/tag/v0.9.15-1): Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.15-1). This release contains some runtime cleanup, like kianenigma’s fix locked deposit of council voters.

Hash: `0xc0d644131338cbf809cdb03afe0f7e1660b228e18011087858828ced4365d82e`

Please feel free to use srtool yourself to check the proposal hash. Make sure to vote at your convenience, it should be upgraded asap to prepare for the next runtime.

Polkadot Runtime Upgrade to v9151

The proposal, upgrading Polkadot Runtime to **v9150**, is up for vote. 

Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.15). This release contains some runtime cleanup, like kianenigma’s fix locked deposit of council voters but also the locked deposits of Nicks pallet.

Hash: `0x960d3ad3f42eb41ab2131e1561dd8cc20f87585e37d2d1b02525578204f11d4b`

Please feel free to use srtool yourself to check the proposal hash. Make sure to vote at your convenience, it should be upgraded asap to prepare for the next runtime.

-------------------------


**UPDATE**

It is advisable to vote `Nay` on Referendum 49. It looks like the runtime upgrade lacked a corresponding Polkadot companion change for #10043, as a result some people may see some errors in the logs of Kusama nodes.

For Kusama an additional runtime upgrade will likely be proposed reverting the issue. Until it is resolved we don't want to risk anything happening on mainnet, so only after we will move to a new upgrade.

Runtime v9150 on Polkadot Network

After Shell successfully processed the runtime upgrade to Statemint and handed over block production to the Statemint collators, they were not able to produce blocks due to a mismatch in key types. Specifically, Aura uses sr25519 keys to sign blocks, but the keys in the genesis chain spec were generated using ed25519.

A new runtime was created as a temporary fix. This runtime enables ed25519 in Aura for Statemint. This will be enacted on the Relay Chain so that validators will be able to validate the collator signatures. After the chain is producing blocks again, a follow up runtime upgrade will migrate Aura back to using sr25519 keys.

Call hash: `0x0e21b5233c7591ee89eca0cae71cf9a9a4c45fe2393075ab33361a673f5d322d`

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

Fix Statemint - Aura Key Scheme

This is a follow up to [Referendum 46](https://polkadot.polkassembly.io/referendum/46), which failed because Polkadot did not have a default XCM version set. This protection, that the Relay Chain will not dispatch messages without a minimum safe version, was put in place after a previous vulnerability. Since this is the first cross-chain interaction that Polkadot has had, the version was not initialized.

The batch of calls contains the same two calls as Referendum 46, with an additional call to set the default XCM version of Polkadot to 2.

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

Upgrade Shell to Statemint (with XCM Fix)

This will be a batch of two scheduled transactions. They would probably work fine at once, but will schedule to be safe and ensure that the `set_storage` takes place prior to authorizing the upgrade.

The first will set some storage keys in Shell for Statemint's "genesis". The second will authorize the upgrade to Statemint. Both calls need to be constructed on Shell and then dispatched from the Relay Chain in an XCM.

See the [release notes](https://github.com/paritytech/cumulus/releases/tag/statemint-v6.0.1) to review the assets, reproduce the `set_storage` call, and generate the runtime.

## Shell Constructions

### Set Storage

The `set_storage` call can be generated with the `build-spec` command from a collator node, using `statemint_genesis.json` as input. See the release notes for more info. Notable storage items include:

- Setting the first set of Aura collators.
- Setting the `SafeXcmVersion` to `2` to protect against older XCM formats.

Call data (statemint_genesis_values.scale):

```
0x0006908015464cac3378d46f113cd5b7a4d71c84476f594316a7dfe49c1f352d95abdaf110000000008015464cac3378d46f113cd5b7a4d71c844e7b9012096b41c4eb3aaf947f6ea4290800008015464cac3378d46f113cd5b7a4d71c845579297f4dfb9609e7e4c2ebab9ce40a0502104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b38015464cac3378d46f113cd5b7a4d71c84579f5a43435b04a98d64da0cefe185054000a0acb9030000000000000000000000801809d78346727a0ef58c0fa03bafa3234e7b9012096b41c4eb3aaf947f6ea42908000080267ada16405529c2f7ef2727d71edbde4e7b9012096b41c4eb3aaf947f6ea429080000083a6300803c311d57d4daf52904616cf69648081e4e7b9012096b41c4eb3aaf947f6ea429080000803c311d57d4daf52904616cf69648081e5e0621c4869aa60c02be9adcc98a0d1d0502104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b3803f1467a096bcd71a5b6a0c8155e208104e7b9012096b41c4eb3aaf947f6ea4290800008057f8dc2f5ab09467896f47300f0424384e7b9012096b41c4eb3aaf947f6ea4290800008057f8dc2f5ab09467896f47300f0424385e0621c4869aa60c02be9adcc98a0d1d0502104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b3805e8a19e3cd1b7c148b33880c479c02814e7b9012096b41c4eb3aaf947f6ea42908000080682a59d51ab9e48a8c8cc418ff9708d24e7b9012096b41c4eb3aaf947f6ea429080000807474449cca95dc5d0c00e71735a6d17d4e7b9012096b41c4eb3aaf947f6ea429080000807b3237373ffdfeb1cab4222e3b520d6b4e7b9012096b41c4eb3aaf947f6ea42908000080c2261276cc9d1f8598ea4b6a74b15c2f308ce9615de0775a82f8a94dc3d285a1040180c2261276cc9d1f8598ea4b6a74b15c2f4e7b9012096b41c4eb3aaf947f6ea42908000080c2261276cc9d1f8598ea4b6a74b15c2f57c875e4cff74148e4628f264b974c80400000000000000000000000000000000080cd5c1f6df63bc97f4a8ce37f14a50ca74e7b9012096b41c4eb3aaf947f6ea4290800002101cec5070d609dd3497f72bde07fc96ba04c014e6bf8b8c2c011e7290b85696bb30b1aeeca675702f24c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421804c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d54212101cec5070d609dd3497f72bde07fc96ba04c014e6bf8b8c2c011e7290b85696bb314f6a7e973c2c34dc5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b76280c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7622101cec5070d609dd3497f72bde07fc96ba04c014e6bf8b8c2c011e7290b85696bb34cb6fa5260704ee40b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b3800b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b32101cec5070d609dd3497f72bde07fc96ba04c014e6bf8b8c2c011e7290b85696bb35242002c980f9df1c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d781180c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d781180cec5070d609dd3497f72bde07fc96ba04e7b9012096b41c4eb3aaf947f6ea4290800003501cec5070d609dd3497f72bde07fc96ba0726380404683fc89e8233450c8aa19502fe5f80e8854f64761757261804c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421804c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d54213501cec5070d609dd3497f72bde07fc96ba0726380404683fc89e8233450c8aa1950a3f059d7e690a34f6175726180c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d781180c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d78113501cec5070d609dd3497f72bde07fc96ba0726380404683fc89e8233450c8aa1950c41649dd3c9d26696175726180c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b76280c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7623501cec5070d609dd3497f72bde07fc96ba0726380404683fc89e8233450c8aa1950fa571e62466b970561757261800b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b3800b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b380cec5070d609dd3497f72bde07fc96ba088dcde934c658227ee1dfafcd6e169030502104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b380cec5070d609dd3497f72bde07fc96ba0e0cdd062e6eaf24295ad4ccfc41d46090504104c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d54214c3d674d2a01060f0ded218e5dcc6f90c1726f43df79885eb3e22d97a20d5421c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c7d7d38d16bc23c6321152c50306212dc22c0efc04a2e52b5cccfc31ab3d7811c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b762c5c07ba203d7375675f5c1ebe70f0a5bb729ae57b48bcc877fcc2ab21309b7620b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b30b2d0013fb974794bd7aa452465b567d48ef70373fe231a637c1fb7c547e85b380d57bce545fb382c34570e5dfbf338f5e4e7b9012096b41c4eb3aaf947f6ea42908000080d5e1a2fa16732ce6906189438c0a82c64e7b9012096b41c4eb3aaf947f6ea42908000080e38f185207498abb5c213d0fb059b3d84e7b9012096b41c4eb3aaf947f6ea42908000080e38f185207498abb5c213d0fb059b3d86323ae84c43568be0d1394d5d0d522c4100200000080f0c365c3cf59d671eb72da0e7a4113c44e7b9012096b41c4eb3aaf947f6ea429080000
```

### Authorize Upgrade

This message authorizes the upgrade of Shell to a runtime with a given hash (statemint_runtime-v601.compact.compressed.wasm). Once the upgrade is authorized, anyone can submit the runtime via `parachain_system.enact_authorized_upgrade`, and it will upgrade 600 blocks (approximately 1 hour) later.

Call data: `0x0103af49687b93d91fc08c1fcea1001d724a95c533a949019645d3e4179beedbf67e`

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

## Polkadot Proposal

This proposal is to schedule these messages to dispatch from Polkadot to Shell. They will dispatch 5 and 20 blocks after enactment to ensure each is processed separately. We give them plenty of weight (100 billion and 1 billion, respectively) to ensure they execute.

Call hash: `0xa6830793b6a3473f66fbd7305a9e330dd2dd688df0e8fcbd0c9ff08d28040a34`

![](https://i.imgur.com/5D8syF9.png)
![](https://i.imgur.com/YmVC8o3.png)


Upgrade Shell to Statemint

The proposal, upgrading Polkadot Runtime to **v9140**, is up for vote. Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.14). This runtime only executes a single change: disabling xcm teleports and reserve transfers as a prerequisite to upgrading Shell to Statemint on the network.

- Hash: `0x317c7862dc523bd083e4dd6545079bdc18058f561bada9e5e5646935b1cc04af`

Please feel free to use srtool yourself to check the proposal hash. Please not this is a runtime-only release. Please vote at your convenience!


Runtime v9140 on Polkadot Network

The proposal, upgrading Polkadot Runtime to v9122, is up for vote. Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.12-1). If enacted, this runtime will be the one supporting the first auctions and crowdloans on Polkadot Network.

- Hash: `0x0f598b97de6adfb2c5edffb7e8e5aed6408d29382a9de372ed229391a20c4a86`.

Please feel free to use srtool yourself to check the proposal hash. This is a **runtime-only** release. Node operators do not need to upgrade. As such, no binaries, package files or docker images have been created for this release.
 
Please vote at your convenience!


Runtime v9122 on Polkadot Network

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

Proposal to Onboard Shell on Polkadot

Proposal for First Parachain Auctions on Polkadot

This is a proposal to schedule the first set of parachain auctions on Polkadot as well as get
Council buy-in to a recommended strategy for scheduling auctions on a 3-6 month basis.

Based on the performance of parachains on Kusama and the state of audits, the Parity engineering
team believes that the code for parachains, auctions, and crowdloans is ready for an initial
production release.

This motion proposes two batches of auctions:

- The first: five auctions, starting 11 Nov, seven days each, beginning every _seven_ days, for
  lease periods 6-13 (LP6 is slated to begin 15 Dec)
- The second: six auctions, starting 23 Dec, seven days each, beginning every _14_ days, for
  lease periods 7-14 (LP7 is slated to begin 09 Mar 2022)

As auctions can take place prior to a lease period starting, this motion schedules auctions to
begin around mid-day (UTC) of 11 November.

In order to ensure stability guarantees, I suggest along with this proposal that the Council and
network governance limit the number of parachain slots on Polkadot to 75% of that on Kusama. This
initial schedule will last until early March; as the network grows the Council can suggest an
updated auction cadence to stay within a reasonable factor of safety relative to the number of
parachains on Kusama.


Proposal for First Parachain Auctions on Polkadot

When submitting the image for the Kusama proposal upgrading the runtime to v9110, we realised the hash used was compact, not compressed. The compact wasm file is too big to be added to the network, therefore a compressed hash needs to be used: [**Motion 117**](https://polkadot.polkassembly.io/motion/117) is now up for vote!  **This motion executes the same upgrade to v9110, this time with compressed hash**. 

The motion proposes an upgrade of the Polkadot Runtime to **v9110** - Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.11). Please feel free to use `srtool` yourself to check the proposal hash. If passed by the Council.

Hash: `0x791e698f3690481e0eb16d35017cf3bb27ec095ec6f27dafd3a230b76dc42f86`

Make sure to vote at your convenience!

Runtime v9110 on Polkadot Network

The proposal, upgrading Polkadot Runtime to **v9110**, is up for vote. Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.11).

Hash: `0xe874dd4219efa603acc0ab24a592d6f1b8553b7aedb196d1ef65fdd7fc3b8fe5`.

Please feel free to use `srtool` yourself to check the proposal hash. Migrations and other important changes in v9100 make it impossible to skip this release - hence why the new vote. If fast-tracked, TC should ensure this is enacted after v9100 in the network and after v9110 on Kusama.

Make sure to vote at your convenience! 

The proposal, upgrading Polkadot Runtime to **v9100**, is up for vote. Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.10).

Hash: `0x8160fd4a5aa5d58491cc8d4f0919780da25feb9ada92c2126b3f1d859800dd81`.

Please feel free to use `srtool` yourself to check the proposal hash. The proposal uses a non compressed version of the runtime. We should aim for the TC to fast-track for enactment only after Kusama's runtime upgrade has been executed. 

Make sure to vote at your convenience! 

Tech. Comm. Proposals