After performing an upgrade on a remote node that includes a new pallet in my runtime, I attempted to sync a local node with the remote one, but I encountered the following error:
Bootnode with peer id `12D..` is on a different chain (our genesis: 0x40b7…db79 theirs: 0xa82a…1bc2)
I have been using the same chain spec
JSON file for both nodes. To test this, I compiled both the remote and local codebases, the latter of which includes the new pallet's code. I ran both nodes using the same chain spec
JSON file. However, as I stated earlier, I encountered an error in the second case.
I'm unable to understand why this is occurring when I'm using the same chain spec for both nodes, which should mean they have the same genesis. Am I wrong or missing something here?
How can I debug this issue?