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

Can't create raw build spec, Getting error Unknown chain identity #1925

Closed
shanithkk opened this issue Mar 26, 2024 · 4 comments
Closed

Can't create raw build spec, Getting error Unknown chain identity #1925

shanithkk opened this issue Mar 26, 2024 · 4 comments

Comments

@shanithkk
Copy link

shanithkk commented Mar 26, 2024

Description

When i trying to build the raw build spec from plain build spec, getting an error like
thread 'main' panicked at node/cli/src/command.rs:44:13: Unknown chain identity

Expected behaviour

Should build the raw spec from the given plain spec

Steps to reproduce

  1. Create plain spec
    /frequency/target/release/frequency build-spec --chain=frequency-rococo-local --disable-default-bootnode >/tmp/frequency-rococo.json
  2. Build the raw build spec
    /frequency/target/release/frequency build-spec --chain=/tmp/frequency-rococo.json --raw --disable-default-bootnode > /tmp/fre-raw.json
@saraswatpuneet
Copy link
Collaborator

saraswatpuneet commented Mar 26, 2024

@shanithkk there is a typo above --chain=frequency-rococ-local -> --chain=frequency-rococo-local

@shanithkk
Copy link
Author

@saraswatpuneet its my bad, actually i ran correct command only
Screenshot 2024-03-26 at 10 13 54 PM

Highlighted. i thing the issue coming due to the chain spec id

@wilwade
Copy link
Collaborator

wilwade commented Mar 28, 2024

@shanithkk Two things that might be the issue.

  1. The change identity changed with the recent update to support the Paseo testnet. frequency-local is the chain value you want to use now for a local run (be it paseo-local or rococo-local)
  2. We limit the chain support depending on the build features. You want to be using cargo build --features frequency-local or if you prefer the release build cargo build --release --features frequency-local (While it can cause confusion like this, it means testcode and production code more more separated)

@wilwade
Copy link
Collaborator

wilwade commented May 3, 2024

Closing as stale. Feel free to reopen.

@wilwade wilwade closed this as completed May 3, 2024
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

No branches or pull requests

3 participants