This repository was archived by the owner on Oct 2, 2023. It is now read-only.
Merged
Conversation
asiniscalchi
approved these changes
Jul 3, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
The issue was the altered chain spec, the chain spec that was used to launch a fresh parachain was from
v0.0.4-devtag and from that commit to the latest there has been several changes tospecs/arrakis.json. Due to that, when trying to sync with the remote node, local node was producing different genesis hash.Another issue was that
spec/arrakis.jsonwas in plain format, when it should be raw. AndchainTypealso should beLiveinstead ofLocal(although for a syncing node, it's not a big deal, but if we were to run a collator,Livechains need to insert keys, etc.)In the future, we should always maintain the chain spec in raw format and make sure to never alter it, except when the chain was reset.
Test
To test this fixes the issue:
this runs the latest binary with the new
arrakis.jsonand you should be able to sync with the remote node.closes #26