substrate-parachain-template

substrate-parachain-template copied to clipboard

<@taulepton:matrix.org> Dan Shields: when you say Rocovo open slots "fairly soon" is that on the order of days or weeks? I'm trying to assess if it's worth trying to deploy to chachacha.

I don't have a solid time, sorry. I would see no harm in testing on #chachacha:matrix.org , it should be rather simple to target your parachchain to both via CLI option and a custom chain spec (like is done for dev vs local)

in fact, I would suggest such a configuration. try the behavior out to change between these maybe? would be curious to see what you discover is best. others here that have parachains deployed on multiple relays may have better advice too

you may need to consider the implications of "hot swapping" a collator between them... the base path may need to be adjusted accordingly for example

It looks like the guys from Kylin have also provided some work instructions for a chachacha deployment - https://kylinnetwork.medium.com/kylin-is-on-chachacha-and-partnered-with-centrifuge-5ce3b3ab73c8

the targeted chains should include rococo local in dev mode and default to rococo live testnet when ready. note the CLI selection of paraid was removed intentionally to prevent misuse, so one must modify the chain spec accordingly to get on rococo after registration

we can follow up with docs describing this on the cumulus tutorial

we can also walk through the generation of a chain spec for rococo thus way naturally. see
https://github.com/substrate-developer-hub/substrate-docs/issues/created_by/bkchr

• https://github.com/substrate-developer-hub/substrate-docs/issues/380
• https://github.com/substrate-developer-hub/substrate-docs/issues/331
• https://github.com/substrate-developer-hub/substrate-docs/issues/513