Better pivx.conf Masternode data error notification #2170
Merged
Conversation
This file contains 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
… to initialize the masternode. Example: if the masternode private key was badly written in the pivx.conf and cannot be parsed, return the error and don't start the node.
random-zebra
added
Masternode
Startup
Fuzzbawls
approved these changes
Jan 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In case of pivxd, if there is for example an invalid masternode private key or an invalid masternode address we are only logging the error (In case of pivx-qt, a visual error popup notification is triggered).
This PR improves the Masternode data error detection exiting early at the node startup (same as we do on every other bad data provided by the user at startup).