A proposal requested by the Manta team to register a new genesis wasm. Contextual information below:

**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.

**Impact / why fast-track?**

After the acquisition of a parachain slot, Manta Network’s core development team has begun a sequence for launching the network. Not having this parachain producing blocks would prevent and delay that launch. The extrinsics called in our proposal affect just our 2104 parachain and it has not completed genesis, so there are no XCMP channels to worry about either, the relaychain should be unaffected by this.

**Remedy** 

After thorough investigation and collaboration with the Parity development team, we've identified a 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.

**Council Proposal**

We humbly request that the technical committee fast-track the proposal to register the correct genesis state and code on Polkadot. This will allow our collators to begin producing blocks.

We have submitted the Preimage for the below proposal:

hash: `0x2d1b0d07d86ebe11297eb5a732d5d56e2b118eb1e8e55b0bdc801c5d313371c9`

in extrinsic [https://polkadot.subscan.io/extrinsic/14362712-2](https://polkadot.subscan.io/extrinsic/14362712-2) from the same account as was used to originally register the paraID/parathread in [https://polkadot.subscan.io/extrinsic/13905786-2](https://polkadot.subscan.io/extrinsic/13905786-2).

**Extrinsics called:**

`batchAll()`

`    - registrar::setCurrentHead(2104, corrected.state)`

`    - paras::forceSetCurrentCode(2104, corrected.wasm)`

New WASM file can be found [HERE](https://github.com/Manta-Network/Manta/actions/runs/4234987640).

registrar.paras(2104) => manager: 15ynbcMgPf7HbQErRz66RDLMuBVdcWVuURhR4SLPiqa6B8jx

Gist by the CEO of Manta Network Shumo Chu: [https://gist.github.com/stechu/9c97c7766951d377accd8835e5da79fb](https://gist.github.com/stechu/9c97c7766951d377accd8835e5da79fb)

Message Text:

"This shall serve to testify that the following Polkadot governance referendum has been initiated and is endorsed by the Manta Network team  - Referendum number: TBD - Proposal hash: 0x2d1b0d07d86ebe11297eb5a732d5d56e2b118eb1e8e55b0bdc801c5d313371c9 - Polkassembly discussion: https://polkadot.polkassembly.io/motion/362"

signature from the account that registered paraID 2104: `0x2478a5e64e8c7915e12ca048a2dfb5d04ff97f188fc1f7948bd77c19446fd421af3555a96ebbb1720b7ac1c548877ff8fc9ad12dcbf095f0aef9d8f54b444087`

call

calls

- Manta Network had a problem with their parachain not producing blocks.
- They found a solution to fix the problem.
- They are asking the technical committee to fast-track their proposal to fix the issue.
- They provided a link to the new WASM file.
- They shared a message and a signature from the account that registered the parachain.

#110 Fix genesis registration for Manta Parachain

No Active Proposals