This proposal aims to enable pre-checking for runtime upgrade on parachains: With pre-checking enabled a parachain is only allowed to upgrade their runtime **after validators have tried compiling it and they agree it is good**, as opposed to just accepting it blindly and then fail when the parachain tries to produce blocks with the new runtime. This is just generally a good idea, exists for a while already and has been successfully tested on Versi, Rococo and Westend. It is also required for rolling out slashing as it helps reducing the risk of unjustified slashes.

Parachains need to support the `go_ahead_signal,` but that should be a non issue as this has been introduced over a year ago.

 - Call to be enacted: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.dotters.network%2Fpolkadot#/extrinsics/decode/0x332901).

Preimage is submitted. Make sure to review and vote at your convenience!

Schedule a majority-carries referendum to be tabled next once it is legal to schedule
an external referendum.

The dispatch of this call must be `ExternalMajorityOrigin`.

- `proposal_hash`: The preimage hash of the proposal.

Unlike `external_propose`, blacklisting has no effect on this and it may replace a
pre-scheduled `external_propose` call.

Weight: `O(1)`

Enable or disable PVF pre-checking. Consult the field documentation prior executing.

- This proposal is about allowing parachains to upgrade their runtime after validators have checked and agreed that it is good.
- This idea has been successfully tested on Versi, Rococo, and Westend.
- It is also needed for rolling out slashing to reduce the risk of unjustified slashes.
- Parachains need to support the "go_ahead_signal," which was introduced over a year ago.
- There is a call to be enacted and a preimage has been submitted for review and voting.

#324 Setting pvfCheckingEnabled In The Configuration To TRUE

No Active Proposals