Rococo slot request from Phala Network

[tolak]

You completed the Parachain Tutorials for your parachain and tested locally?

• Yes, we have successfully tested our chain on rococo-local.

Team Name

Phala Network

Parachain Name

Rhala

ParaID

2004

Parachain Manager Account

5FNUsoMKdSFpPs7dcgzgqtRmoH2zDbs9eqwAMKLNWD2LkLjc

Is this for a short or long term slot?

Long-term: we have secured a slot on Polkadot or Kusama.

Upload your Genesis Head (genesis state) - Do not submit a compressed file.

https://github.com/tolak/parachain-res/blob/main/rhala/2023-11-08/rhala-staging-state.hex

Upload your Validation Code (genesis runtime Wasm) - Do not submit a compressed file.

https://github.com/tolak/parachain-res/blob/main/rhala/2023-11-08/rhala-staging-code.wasm

(Optional) Upload your Chain Specification

https://github.com/tolak/parachain-res/blob/main/rhala/2023-11-08/rhala-staging-raw-spec.json

Anything else we should know?

Please open HRMP channel with following project's Rococo parachain:

• Moonbeam
• Astar
• AssetHub
• BridgeHub (if have)

Register your Rococo parachain details for polkadot-js/apps

• Polkadot-js Apps UI PR completed
  • Available here

[tolak]

Hi @al3mart, please help register our Rococo parachain, the code is based on polkadot-sdk v1.2.0

[paritytech-onboard-rococo-p-chain]

Parachain is now being onboarded.

[tolak]

@al3mart @AlexD10S, we have inserted the session key and restart our collator, but still hasn't started produce block, can you help check if the runtime already is the one I provided? Because I found the runtime version shown in polkadot.js.app still is the old one

[AlexD10S]

Yesterday there was an issue with Rococo and it was not generating blocks. Now is working again, do you see any error messages?
I can try to set the state and wasm manually again.

[nanometerzhu]

@AlexD10S there is an error message repeat and repeat: [Parachain] Could not find the header of the genesis block in the database! block_hash=0x2c0c4eaa199decaf7410c4764a7f88e17eaa04a188b0d025397a15839cb4b6bf

Updated: I found previously rhala.phala.network points to a wrong server. Now the DNS record has been fixed, and the correct genesis block is 0xe0baa740e6aff1d5616cda3f16c5f51ac96bbbd9899583f028045f6ac7e86c5c. Please help to fix. Thanks!

[tolak]

@AlexD10S can you on this? Let me know if we need to create a new issue, since this one was closed by the bot

[AlexD10S]

I am reopening the issue and we can work on this one. The error is Could not find the header of the genesis block in the database

I see in some StackExchange question that restarting the node fix it: https://substrate.stackexchange.com/questions/6651/how-to-rescue-a-parachain-from-could-not-find-header-of-the-genesis-block-in-th

But I am going to research it more

[tolak]

@AlexD10S Thanks, please let us know if the log is help

[AlexD10S]

I have reset the genesis and wasm files with the ones provided in this Issue, let me know if you are still seeing the same log

[tolak]

@AlexD10S Just confirm is the genesis header you set is this one? 0xe0baa740e6aff1d5616cda3f16c5f51ac96bbbd9899583f028045f6ac7e86c5c

[AlexD10S]

Ahh no, I updated with the one provided in the Issue.
Sorry I missed the update of the previous message, should I update with 0xe0baa740e6aff1d5616cda3f16c5f51ac96bbbd9899583f028045f6ac7e86c5c ?

[tolak]

@AlexD10S yes, please update with this one

[AlexD10S]

Done