Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Synch chainspec path updates #320

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

chore: Synch chainspec path updates #320

wants to merge 2 commits into from

Conversation

ggera
Copy link
Member

@ggera ggera commented Jul 18, 2024

fixes NO Ticket

In relation to KILTprotocol/kilt-node#643

Checklist:

  • I have verified that the code works
  • I have verified that the code is easy to understand
    • If not, I have left a well-balanced amount of inline comments
  • I have left the code in a better state
  • I have documented the changes (where applicable)
    • Either PR or Ticket to update the Docs
    • Link the PR/Ticket here

@ggera ggera requested review from ntn-x2 and Ad96el July 18, 2024 12:06
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-320.d3oeht7cvddn19.amplifyapp.com

@Ad96el
Copy link
Member

Ad96el commented Jul 18, 2024

lets wait for the release

@ChrisChinchilla
Copy link
Contributor

@Ad96el What release version and when? As I am also testing some mechanisms for versioning.

@Ad96el
Copy link
Member

Ad96el commented Jul 19, 2024

It will be version 1.14.0. I think we will have it in two sprints.

Copy link
Member

@ntn-x2 ntn-x2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There will be a minor breaking change for the export-genesis-state command, not sure if it's shown anywhere in the docs.

@@ -40,8 +40,8 @@ The KILT parachain accepts an additional parameter to select the environment to
This can either be `peregrine` or `spiritnet`.

Hence, to start a full node for the Spiritnet network, the parameter would be `--chain=spiritnet`.
Unfortunately, there is no hardcoded chain spec for the Peregrine network, so the full path of the chainspec file must be provided `--chain=/node/dev-specs/kilt-parachain/peregrine-kilt.json`.
Please refer to the [KILT node repository](https://github.com/KILTprotocol/kilt-node/blob/master/dev-specs/kilt-parachain/peregrine-kilt.json) or the [Docker image](https://hub.docker.com/r/kiltprotocol/kilt-node/tags) for more information.
Unfortunately, there is no hardcoded chain spec for the Peregrine network, so the full path of the chainspec file must be provided `--chain=/node/chainspecs/peregrine/peregrine-paseo.json`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have it now, it's called "peregrine"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants