Fix incorrectly enacted referendum caused by a Substrate bug
Democracy
1 Comments
Tabled

Proposal
###
A proposal by the Polkadot Council, and later to be voted by the community for the final decision, to fix the issue with the enactment of the recently executed referendum #113, submitted by Watr.
###
Context
###
Referendum #113 was enacted, and after the execution of the two extrinsics from the preimage, the runtime was correct, and the header was correct, but the header got overwritten. The header was overwritten via inherent transaction from the collator. This transaction was supposed to be rejected. Still, it was not rejected due to a Substrate bug: https://github.com/paritytech/substrate/issues/9210
The issue now needs to be fixed by re-executing one of two extrinsics from the previously executed referendum to set the correct header of the parachain.
###
Impact
###
The network runtime is in the correct state after the execution of the previous proposal to reset the parachain. Still, due to the incorrect head, the parachain cannot produce blocks.
###
Remedy
###
The execution of one of the extrinsic to set the Watr’s parachain (2,058) head from the previously executed governance proposal will fix the issue.
###
Proof of Authencity
###
We confirm the intention to reset the head of the Watr parachain (id: 2058) to 0x0000000000000000000000000000000000000000000000000000000000000000001a3a2baafaa9623dbeab06759b78f4bce878d0fbfeef992a546bce6670131e6103170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400 to resolve the issue caused by a bug in the enactment of referendum 113
###
Signature

0x9618272c953c90b67973d2525bead280ea74f71d0104b267767b9312f7785f28ec683f269d565d6faf4927faa4262730b4939e71fea292be50be7e5b1f9bb987
###
Below is the preimage:

  • Hash: 0xac9ff5733f194470235d78f67d56e656a0d8ee8a908dda7782d22ed2dfb9f9eb

  • Extrinsic: paras.forceSetCurrentHead(2058, newHead)

Reply
Up
Share
  • Business
  • Call
  • Metadata
  • Timeline2
Comments

No comments here