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

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

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

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

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

Please note this proposal should be rejected.

______________________
_______________________
_______________________

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


**Runtime**

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

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


Proposal hash: `0xbd78d3542767047aba0babb8c8825a5799e3ef54a21193ffe24b98eb4f895162`

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

- There is a proposal to upgrade Polkadot's runtime to version v9320.
- The proposal includes several changes and updates to the code.
- The proposal has a specific hash that can be reviewed.
- The community will need to vote on the proposal in the referenda queue.
- The proposal is an external motion, meaning it needs to be voted on by the community after the Council vote.

#89 [PLEASE REJECT] Runtime v9320 Upgrade On Polkadot

No Active Proposals