Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Fix new node sync in MVP #88

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Fix new node sync in MVP #88

merged 1 commit into from
Jan 11, 2024

Conversation

gdethier
Copy link
Contributor

  • While syncing a new MVP RPC node, sync fails at some point with this error: 💔 Verification failed for block 0x2b4e96021b427ac071238e530dd1a10993c6e22bea6d61f106358d31ed0c3212 received from (XXX): "Bad signature on 0x2b4e96021b427ac071238e530dd1a10993c6e22bea6d61f106358d31ed0c3212" (XXX stands for any node peer ID and is not relevant here)
  • This error already occurred in the past but has been circumvented by an ugly direct DB copy from one node to the new one
  • After some investigation, it turns out that there seems to be a solution: Aura: Adds some compatibility mode to support old chains paritytech/substrate#12492
  • This PR enables compatibility mode on MVP chain

@gdethier gdethier changed the title New node sync fails in MVP Fix new node sync in MVP Jan 11, 2024
Copy link
Contributor

@benoitdevos benoitdevos left a comment

Choose a reason for hiding this comment

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

👍

@gdethier gdethier merged commit 15c6060 into main Jan 11, 2024
2 checks passed
@gdethier gdethier deleted the feature/fix-sync branch January 11, 2024 13:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants