Fix genesis registration for Manta Parachain
Democracy
8 Comments
Tabled

What Happened

Our parathread was registered on the Polkadot relaychain, obtained a parachain slot and was upgraded to a parachain. However, we encountered a minor setback when the genesis collators failed to produce blocks on the new chain. It turns out that the registration process contained incompatible genesis WASM and state files, which caused our parachain to be stuck at genesis.

Remedy

After thorough investigation and collaboration with the Parity development team, we've identified an solution to the issue. With assistance from Polkadot governance, we can correct the incompatible parachain state & WASM files that were originally registered. This correction will not have any impact or loss of state since the chain has never produced any blocks. We believe that this is the most efficient and effective solution to get our parachain up and running.

Extrinsics called in this proposal:

  • batchAll()
    • paras::forceSetCurrentCode(2104, corrected.wasm)
    • registrar::setCurrentHead(2104, corrected.state)
Edited
Polkassembly
Reply
Up
Share
Second
No current seconds
This proposal has been turned into referendum.
Metadata
hash
0x56248eb53eb90f343a9f5623cb56e302daba1b33073fd70738f3611d8daf57f0
deposit
240 DOT
proposer
Call
Table
callIndex0x1a02
sectionutility
methodbatchAll
args
Large data, please check it on subscan
TimelineLatest activity undefined
2023-03-04 22:03:18
Proposed
Index
#26
2023-03-05 08:42:30
Tabled
Referendum Index
#108
Deposit
240 DOT
Depositors
0
Comments
SubSquare(2)
Polkassembly(6)

Could someone explain why it's being 'Nay' voted? New to all this.

Reply
Up

https://polkadot.polkassembly.io/referendum/110 is a fast-tracked motion with the same goal as this one.

Please reject #108

Reply
Up