Error out at startup if there was an internal problem during DMN init #2745
Conversation
This file contains hidden or 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
furszy
force-pushed
the
2022_init_dmn_error
branch
from
a864996 to
32edd63
Compare
Author
|
Added two more fixes that were blocking the completion of the distributed key generation protocol:
|
furszy
force-pushed
the
2022_init_dmn_error
branch
from
32edd63 to
f48176b
Compare
Author
|
rebased after 2742 merge, ready to go. |
Fuzzbawls
approved these changes
Feb 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-up to #2742.
Notify user if the Deterministic MN initialization failed for a local non-recoverable error.
Moved the startup Masternode activation after the connection manager initialization.
Without it, as the network module isn't initialized, the MN connectivity check always fails.
Removed an overkill check that was rejecting incoming connections on Masternodes if the node wasn't, tier two wise, synchronized.
The tier two sync preference for outbound connections can, and will, be achieved differently on a subsequent PR.