This repository has been archived by the owner on Dec 16, 2021. It is now read-only.
fix: ProRegTx is not confirm #69
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
thephez
reviewed
Jun 11, 2020
There was a problem hiding this comment.
FYI - you can see the minimum conf requirements for the various networks in the nMasternodeMinimumConfirmations setting in Core (e.g. here for testnet). Looks like all networks other than mainnet use 1.
shumkov
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue being fixed or feature implemented
Masternode list was empty after successful masternode registration
What was done?
Wait for 1 confirmation after ProRegTx broadcasted.
How Has This Been Tested?
Manually
Breaking Changes
No
Checklist:
For repository code-owners and collaborators only