#53 Polkadot Runtime Upgrade to v9170 and Statemint Runtime Upgrade to v700
Please note this is a batch call proposal, combining the Polkadot upgrade with the Statemint upgrade:
- Batch call hash:
0xbf60cbdd406036e0b6a3028763bfe20d9569780c0ffddc75cf209358fce3111c - Call design: here.
The Polkadot runtime will be upgraded to v9170 - Release notes, runtime changes and proposal hash can be found HERE. This release improves the block time degradation issues, as seen on Kusama. 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”.
- Call hash for polkadot upgrade:
0x8eb2806cbdf1a4ba91334669b2476870134db3af5c77f418152af0ad354d3b32
The Statemint runtime will be upgraded to v700:
-
The Uniques pallet includes an extra storage item 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 and Cumulus 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.
- Hash:
0x8adb4ccdf996f05fa7941ce3b56ecec6dd49a88d9db445963e813ac10cadd326. - Encoded call:
0x01028adb4ccdf996f05fa7941ce3b56ecec6dd49a88d9db445963e813ac10cadd326 - Runtime release can be found HERE.
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!
Show More
CP287, would you mind editing the description so we show the example ? :) Also, a short description of the reason why you think your proposal is good would be nice (Although I personally already seconded it).
Chevdor, I still cant do that, cause i cant link my address to my account. The reason for that is because polkadotjs extension support import only from the seed.
About proposal: still think that it is necessary to slowly increase the number of validators until this interferes with the stability of the network, and do it fast enough. This will allow the number of nominations not to exceed 64. This will allow new members to become validators, and not just to generate accounts for existing members. This will allow us to test the capabilities of the network in this direction. If we do this fast enough, it will even lead to greater decentralization (on the contrary, if we do not do this, soon only large companies will remain in the validators, each of which will hold 40-50 validators, and which ultimately grealy increase commissions for nominators).
Oh I get you... now that makes sense. It unfortunately does not look like it will come: https://github.com/polkadot-js/extension/issues/185#issuecomment-546227834
Not sure if you know about this one, it is interesting to know:
I made a proposal that may help addressing this issue here https://github.com/paritytech/polkassembly/issues/719
https://github.com/polkadot-js/extension/issues/185#issuecomment-546227834
This one help! Thanks a lot, Chevdor!
Discover similar proposals
Voted Aye