al3mart / para-onboarding Goto Github PK

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

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

Team Name

Test

Parachain Name

Test

ParaID

4286

Parachain Manager Account

5CvkguduE5zDYCozyawTftRQPZqBR7wFfWuc2ZuzK4xSg48j

Is this for a short or long term slot?

Short-term: we registered a parathread with the paraID above.

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

para-2000-genesis-state.txt

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

para-2000-wasm.txt

(Optional) Upload your Chain Specification

No response

Anything else we should know?

So... We want to start a XCM channel with X parachain with Y paraID...

Register your Rococo parachain details for polkadot-js/apps

• Polkadot-js Apps UI PR completed
  • Available here: {FIX ME!!!!}

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

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

Team Name

Testing2

Parachain Name

Testing2

ParaID

4290

Parachain Manager Account

5FHneW46xGXgs5mUiveU4sbTyGBzmstUspZC92UhjJM694ty

Is this for a short or long term slot?

Short-term: we registered a parathread with the paraID above.

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

para-2000-genesis-state.txt

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

para-2000-wasm.txt

(Optional) Upload your Chain Specification

No response

Anything else we should know?

So... We want to start a XCM channel with X parachain with Y paraID...

Register your Rococo parachain details for polkadot-js/apps

• Polkadot-js Apps UI PR completed
  • Available here: {FIX ME!!!!}

Refactor the code to remove the api initialisation from the functions themselves and just do it once in main maybe, then pass the api along as needed.

We should avoid doing individual transactions in favor of changing the code in calls module to return the calls instead of sending them, then gather all the relevant calls and create one batch containing all of them.

This way we assure the result of the execution is just sending one transaction, avoiding leaving the process half way because of a disconnection or similar scenarios.

Per the diagram in this repo README, in any specific order:

• Check if the para being onboarded needs a permanent or temporary slot, if any - #1
• Paras being onboarded that doesn't exist in Rococo need to be registered
• Manager for the para needs some initial funds #13
• #6
• Remove manager lock from the onboarded para #10
• Para sovereign account needs some initial funds #10
• Integrate with Github issues - maybe Github actions #12 (needs iteration)
• Proper key management

As per the title, the idea would be making the program non dependent on RPC nodes by integrating a light client.
Maybe this can be done in two steps:

• a first one where we have both functionalities and users can choose if connecting to an RPC or launching a light client with some flag
• a second phase where connecting to an RPC is not an option and only light clients are used to query information and send transactions to the network.

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

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

Team Name

a

Parachain Name

a

ParaID

a

Parachain Manager Account

a

Is this for a short or long term slot?

Short-term: we registered a parathread with the paraID above.

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

a

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

a

(Optional) Upload your Chain Specification

a

Anything else we should know?

So... We want to start a XCM channel with X parachain with Y paraID...

Register your Rococo parachain details for polkadot-js/apps

• Polkadot-js Apps UI PR completed
  • Available here: {FIX ME!!!!}

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

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

Team Name

Testing

Parachain Name

Testing Script

ParaID

4290

Parachain Manager Account

5CvkguduE5zDYCozyawTftRQPZqBR7wFfWuc2ZuzK4xSg48j

Is this for a short or long term slot?

Short-term: we registered a parathread with the paraID above.

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

para-4290-genesis-state.txt

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

para-4290-wasm.txt

(Optional) Upload your Chain Specification

No response

Anything else we should know?

So... We want to start a XCM channel with X parachain with Y paraID...

Register your Rococo parachain details for polkadot-js/apps

• Polkadot-js Apps UI PR completed
  • Available here: {FIX ME!!!!}

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

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

Team Name

TEAM NAME

Parachain Name

PARA NAME

ParaID

PARA ID

Parachain Manager Account

ACCOUNT

Is this for a short or long term slot?

Long-term: we have a matching paraID in use on Polkadot or Kusama.

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

GENESIS HEAD

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

VALIDATION CODE

(Optional) Upload your Chain Specification

SPEC

Anything else we should know?

So... We want to start a XCM channel with X parachain with Y paraID...

Register your Rococo parachain details for polkadot-js/apps

• Polkadot-js Apps UI PR completed
  • Available here: {FIX ME!!!!}