Skip to content

Conversation

lightclient
Copy link
Member

fixes #32672

This is kind of a band aid solution since it fixes the issue by bypassing the snap sync expectations of an empty db and attempting to import the new payload if we're at block 1. The next FCU will set the status to synced.

Will continue looking to better understand how the above issue arises and find a more thorough solution.

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.

Snap syncing at genesis of new network causes corrupt db
1 participant