Fixing Inclusion Issues On Parachains Side
This morning CEST Kusama parachains stopped including blocks. The cause was a dispute in a finalized block that stopped the inclusion of new blocks from parachains.
After the chain issued a revert, it "freezes" the current chain to not include any new parachain candidates. As the block was already finalized, we could not revert to and continued producing on this chain. So, the chain currently is rejecting any new parachain candidates. force_unfreeze reverts the freeze. This proposal aims to fix this, for chains to continue with block inclusion.
Info on all submissions below:
-
Preimage for the Fellowship referendum: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2000882c0090e492d7fc2315e0ad47eb060fe96b2c428260eb15ede5519d1476a962d0a0fc
-
Fellowship referendum to whitelist the call: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x17002b0f022cd47cef425d196e70628486dd854a8ce1a41f5d211d26790908f83b64196d4022000000010a000000
-
Preimage for the public referendum:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2c033e00
-
Public referendum to dispatch the call: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x15002b0d02d9c7afcffeb2bc4639716f13d6d5e5bc1e1ca12846cb5931fe0596a195b193d804000000010a000000
Please note that Fellowship is already voting on a proposal that whitelists this hash. Make sure to review, and vote at your convenience!
Comments (6)
Proposal Passed
Summary
0%
Aye
0%
Nay
Aye (261)0.0 DOT
Support0.0 DOT
Nay (1)0.0 DOT
How we can to know, which validator missed parachain block and which parachain it was?
Once the fix is applied, please provide a post mortem as well.