-
Notifications
You must be signed in to change notification settings - Fork 29
Add chainstate storage version mismatch check #1098
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
Conversation
6725b7a
to
197521d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good enough for now. Just one minor suggestion but it's fine to ignore it.
26495ca
to
9c4a229
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides some clean up, this is good to go. We'll add functional tests later.
ChainConfig::magic_bytes
andChainType::name
. They are now stored in db and if mismatch the db is clean up and synced from scratch.clean-data
command which cleans up data directory before starting the node. Except for the lock file.