This proposal will fail in enactment, so external 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:
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:
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: more information can be found on the release notes.
Runtime
pallet-contracts
to weightv2call
multiplierupdate
withdrawreasons
configurableforce_open_hrmp_channel
callpallet-multisig
benchesThis release also contains the changes from v0.9.31 to v0.9.32:
--database
cli argument case insensitive again.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.
set_code
call to always fail.0xbd78d3542767047aba0babb8c8825a5799e3ef54a21193ffe24b98eb4f895162
.