Fix genesis registration for Manta Parachain
Democracy
8 Comments
Started

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
Votes
50%Aye
50%Nay
Aye
0 DOT
Nay
0 DOT
Turnout
0 DOT
Electorate
0 DOT
Failing
Check all votes
Metadata
Proposer
Hash
Delay
0
End
0
Threshold
Call
Table
callIndex0x1a02
sectionutility
methodbatchAll
args
Large data, please check it on subscan
TimelineLatest activity undefined
2023-03-05 08:42:30
Started
referendumIndex
108
voteThreshold
SuperMajorityApprove
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