V0.12.0.x pre-enabled status from masternodes #484
Closed
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
… initial one (from mnb)
UdjinM6
force-pushed
the
v0.12.0.x
branch
2 times, most recently
from
d011d7e to
b0e718a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Treat MN as pre-enabled while there is no legit ping that differ from initial one (from mnb). Should give MN owners info if remote MN was actually enabled and sending pings as expected or was it not enabled and could be delisted in an hour because of no pings. Currently it is shown as enabled regardless which could be confusing.
Rebased resurrection of #481