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

Untitled - public proposal #16

Untitled - public proposal #8

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

Untitled - public proposal #2

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! 

Runtime v9100 on Polkadot Network

The staking team requested a new proposal to increase the minimum bond and allow new nominators above the threshold to participate in the network’s security mechanism. As mentioned by the Staking team on [this message](https://matrix.to/#/!FdCojkeGzZLSEoiecf:web3.foundation/$YNsqfhHKXoRbW_QKvtG5EKn8HodUGFts6abJJdSAoVA?via=matrix.parity.io&via=matrix.org&via=corepaper.org), Polkadot currently has 22500 nominators and the configuration of the staking system prevents further nominators to join.

The team suggests to update the staking parameters: The proposal has the goal to increase the minimum bond to allow new nominators above the threshold to participate in the network’s security mechanism, and for less staked nominators to be chilled. **Note that after the latest runtime upgrade (9090), existing nominators can always update their preference at all conditions.**

The proposal the team suggested aims to change the staking parameters to allow more nominators with higher backing stake be able to join the staking system. The existing parameters as follows:

- Minimum validator bond: None
- Maximum validator count: `1200`
- Minimum nominator bond: `80` DOT
- Maximum nominator count: `22500`
- Chill threshold: 90%

The new proposed parameters aim to update one value:

- New minimum nominator bond: `120` DOTs

The team aims to increase the limit enough so that we won't need to do another tweak for at least a month. **Multiple tracks of optimization are ongoing by the development team**, and you can read more about them on this [issue](https://github.com/paritytech/substrate/issues/9511). Furthermore, a monthly progress report will be released [here](https://gist.github.com/kianenigma/aa835946455b9a3f167821b9d05ba376) to communicate the technical details. Please note that increasing the value of the parameter to **120 DOTs** will hopefully give the team another more time until the new threshold is reached and we have made progress on a more permanent solution. Please leave your comments and feedback on the proposal. Keep in mind these measure is **temporary**, and the overall goal is the stability and security of the network.

- Preimage [HERE](https://drive.google.com/file/d/10FRH_Hzs8kqwI_lfMZhC6bu6Dt0bQdCf/view?usp=sharing) - submitted.
- Hash: `0xb862a50c4e8541c013637e9766f3059af75218f0f9630dc8b6c85dc8f633a971`

Please vote at your convenience!

Increasing nominators’ min bond on Polkadot

Untitled - public proposal #4

The proposal, upgrading Polkadot Runtime to **v9090**, is up for vote. Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.9). If you develop & maintain applications for Polkadot, please note there is [a breaking change](https://github.com/paritytech/substrate/pull/9462) on this runtime.

Hash: `0x6f7f0451388d9053db17c61c67678fdd0d775f9c74dc46ebea565ad0cd52bd6e`.

This proposal uses the NON COMPRESSED runtime.

Please feel free to use `srtool` yourself to check the proposal hash. Make sure to vote at your convenience!

Runtime v9090 on Polkadot Network

Untitled - public proposal #5

As mentioned by the Staking team on [this message](https://matrix.to/#/!FdCojkeGzZLSEoiecf:web3.foundation/$YNsqfhHKXoRbW_QKvtG5EKn8HodUGFts6abJJdSAoVA?via=matrix.parity.io&via=matrix.org&via=corepaper.org), Polkadot currently has 22500 nominators and the configuration of the staking system prevents further nominators to join. 

The team suggests to update the staking parameters as soon as the next runtime upgrade happens today. The proposal has the goal to increase the minimum bond to allow new nominators above the threshold to participate in the network’s security mechanism, and for less staked nominators to be chilled. Note that after 9080, the existing nominators can always update their preference at all conditions. 

The proposal the team suggested will change the staking parameters to allow more nominators with higher backing stake be able to join the staking system. The existing parameters as as follows:

* minimum validator bond: None
* maximum validator count: `1200`
* minimum nominator bond: `40` DOTs
* maximum nominator count: `22500`

**The new proposed parameters will update one value:**
* new minimum nominator bond: `80` DOTs

 and set a new parameter that did not existed before:
* chill-threshold: 90%

The reasoning behind the new minimum nominator bond: Polkadot onboards ~150 nominators per day. That means if the network has 4500 empty slots, they will be filled in 30 days. The team aims to increase the limit enough so that we won't need to do another tweak for at least a month. Changing this parameter to `80` will almost expose 4500 nominators. 

The new chill-threshold will ensure that the permissionless `chill_other` can only be used when more than 90% of "maximum nominator count" is used.
note that to ensure polkadot's stability until the parachains launch, this motion does not yet include an increase in the total count of nominators. Multiple tracks of optimization are ongoing by the development team, and you can read more about them in this [issue](https://github.com/paritytech/substrate/issues/9511).

Please note that doubling the value of the parameter to `80` DOTs will hopefully give the team more time until the new threshold is reached and we have made progress on a more permanent solution. Please leave your comments and feedback on the proposal. Keep in mind these measures are temporary, and the overall goal is the stability and security of the overall network. 


- Preimage can be found [HERE](https://drive.google.com/file/d/1ZdXO1y6_UUlsjaPZgNla6elaMUQgtOxS/view?usp=sharing).

- Hash: `0xc8ca426c26fc637ab82f56e69e91469c6c7205b01609e7970c0ed11cc0c7981f`
- Encoded call data: `0x07170040b743ba00000000000000000000000000000000000000000000000000000001e457000001b0040000015a`

Increasing nominators’ minimum bond on Polkadot

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

This release introduces a **new host function**: As such, node operators should upgrade before the next runtime upgrade on their chain in order to continue being able to sync the chain. 

Please vote at your earliest convenience!

Runtime v9080 on Polkadot Network

Untitled - public proposal #6

The proposal will upgrade the nomination limits such that more people can start nominating. Note that this is a time-sensitive action, because currently existing nominators cannot change their intentions. [This pull request](https://github.com/paritytech/substrate/pull/9193) will change this logic, so that those who are already a nominator will not be affected by any limit, and **will be placed in the next Polkadot  runtime upgrade**.

The new limits increase the nominator capacity by `2500` (making it `22500` in total), and increase the the stake threshold to `40DOTs`. It is intended that these numbers would keep the current count of nominators (all of whom must have 40 or more DOTs) below the new count limit (`22500`) **until the next runtime upgrade**: If an influx of nominators is observed over a very short period of time, the stake limit might need to be increased again proportionally to keep the staking system stable.  

Preimage [HERE](https://drive.google.com/file/d/1Pp8mkUkFCkYiauUAe2RXFBhzk5wgulGV/view?usp=sharing).

Please vote at your convenience!

Upgrade the nomination limits on Polkadot

The proposal **sets a limit on the maximum number of validators**, namely `1200`, and leaves the rest of the parameters unchanged (`20000`/`20DOTs`) for nominators. This proposal started as an **external motion**, meaning that if the Council passes this, the community needs to vote in referenda queue to be executed. 

The validator community should be aware that the discussion around minimum DOT stake limit for validators (similar to what was imposed recently on nominators) has already begun [on the Polkadot Direction channel](https://matrix.to/#/!OwgojQyBzTlUQGGLhq:matrix.parity.io?via=matrix.parity.io&via=matrix.org&via=corepaper.org), and will be proposed **as soon as discussion reaches consensus**. Similar to the nominator limits, **these limits are for the safety of the network and will grow as the network grows.**

The preimage of this proposal can be found [HERE](https://drive.google.com/file/d/1W8J1zSPobzNMSAoAWaSeTWvLRI7QdmwH/view?usp=sharing). 

Context on why this is needed and an explanation of the scaling issues we are seeing on Polkadot Network can be found on the [last runtime upgrade post](https://polkadot.polkassembly.io/motion/88).

Please vote at your convenience!

Limit on the maximum number of validators, based on scaling issues

The proposal, upgrading Polkadot Runtime to v9050, is up for vote. Release notes, runtime changes and hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.5). This release resolves the scaling issues we are seeing on Polkadot Network with staking, introducing hard limits on the number of nominators on chain: which is configurable with governance.

- Previous discussions about the runtime upgrade on the Polkadot Direction channel can be found [HERE](https://matrix.to/#/!OwgojQyBzTlUQGGLhq:matrix.parity.io/$EVsIkHKQaZHNrnOCSrLWwE918yPa3u6srpziFs4usvo?via=matrix.parity.io&via=matrix.org&via=corepaper.org).
- Wei’s post on Polkadot’s staking election situations, problems and discussions about potential solutions can be found [HERE](https://corepaper.org/polkadot/staking/). 
- The blogpost by Polkadot explaining the staking limitations and changes with this runtime upgrade proposal can be found [HERE](https://polkadot.network/polkadot-and-kusama-staking-changes/).

Please vote at your earliest convenience!

Runtime v9050 on Polkadot Network

**UPDATE: Please be so kind to reject this proposal, the team has included the heap pages increase on an upgrade and this seems to be the best way to approach the issue.**

---

We’ve noticed that some validator nodes on polkadot, encounter a “allocator failed to allocate memory” error around the time when the staking election (phragmen) is being computed. Recall that this computation is happening in an **offchain worker thread**. Nonetheless, in the current implementation, the offchain worker thread, which itself is executed in WASM, uses the same WASM environment as the canonical runtime, and therefore has limited memory. To prevent the situation where no validator submits an election solution, the amount of memory accessible to the offchain worker environment should be increased.

Note that ideally, this change should only affect the offchain worker thread, and not the main runtime. But as mentioned, currently they share the same configurations. A long term solution is to separate these configurations and only increase the amount of memory that is accessible to the offchain worker ([PR](https://github.com/paritytech/substrate/pull/8885)). But, since this is not readily possible, we opt to propose increasing the overall WASM runtime memory pages, which affects both block execution and offchain worker. We expect this decision to have **no notable effect** on the main runtime’s progress and execution.

The amount of memory available to WASM is determined in the number of “pages of memory” that can be allocated in the called, aka. “**Heap pages**”. This value lives on-chain, and you can inspect it similar to other [well-known-keys via “:heappages](https://github.com/paritytech/substrate/blob/28107d402cb88cf50119c4ecb16555fcacf3a3e6/primitives/storage/src/lib.rs#L166)”. Currently, no value is set there and a [default of 1024](https://github.com/paritytech/substrate/blob/ef0e22e11535abaa393122209f83ed02a068a464/client/executor/src/native_executor.rs#L48) is used.

More info can be found [HERE](https://docs.google.com/document/d/12CFQlgBxWwBOcpyoJiNhifvAoPQKBDej9f3YRf9Moq8/edit?usp=sharing). This proposal is a temporary solution, Kian from Parity is working on a permanent fix [here](https://github.com/paritytech/substrate/pull/8885).

Preimage for the motion [HERE](https://drive.google.com/file/d/1p1gQKqzYKo2CL-GrsZI2qNonH_kwGZXG/view?usp=sharing).

Increasing the WASM heap pages.

Hello. My name is Jonathan Kleiman. I am a Polkadot ambassador candidate, and I have been a lawyer in Toronto for 10 years. I am licensed by the Law Society of Ontario. You can find my website at www.jkleiman.com, and you can peruse my google reviews [here](https://g.page/kleimanlaw?share). 

As a lawyer, I am licensed to verify documents as a notary. My intention is to verify legal name identities on-chain using this same process. Specifically, I will require two pieces of photo ID, and a short video call to confirm that the person seeking identification is indeed the person on the ID's provided. 

The video call (no, a screenshot - see edit) will be recorded for verification records, but will not be shared without requestor's consent or a court order, if for some reason the requestor needs to prove that their identity was properly verified.

As a lawyer, the risk to me of publicly confirming somebody's identity incorrectly is very serious, as the public would be assured of the reliability of such verification and would be able to rely upon it as if it were notarized by me. For this reason, verifications performed by me will be completely trustworthy, without question.

I plan to charge 5 DOT (3 DOT, see edit) for the verification services. Any voters for this proposal when it reaches referendum will receive their verification for free by fee refund once the proposal is approved (unless this is disallowed)

Please feel free to send any questions or suggestions to me at [Jonathan@JKleiman.com](mailto:jonathan@jkleiman.com)

[Proof of License](https://lso.ca/public-resources/finding-a-lawyer-or-paralegal/directory-search/members/lawyer/049/jonathan-louis-kleiman)

EDITS: 

1) I am lowering the price to 3 DOT, given the recent and anticipated price appreciation

2) Pursuant to comments, I suggest that no video be recorded, but that a screenshot of the video be taken and held on offline storage.

3) I will offer to verify email, twitter, and element name as well.

4) Non-english identification can be done, but must involve a lawyer licensed to practice in the jurisdiction that the account holder resides, who can certify the identity for the Registrar.

5) In the event that there are too many for one person to handle, additional lawyers can be involved to verify identities, but the main registrar would still be responsible to ensure the process is secure and reliable. This practice is acceptable to my law society as well - I am allowed to rely on the certification of a person's identity as long as it is done by a lawyer in their jurisdiction, and I am able to confirm the lawyer's identity and their license to practice law, and receive ID of the account holder.

6) Thank you to those who have participated in the discussion, and those who have foregone staking rewards by seconding my proposal.
