Allow up to MASTERNODE_MAX_MIXING_TXES (5) DSTXes per MN in a row #2552
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.
Currently we only allow one single dstx per mn in a row but that's from a perspective of a local node and when half of the network goes down and getting rebuilt from scratch this restriction got all messed up and nodes start producing dstxes which are refused to be processed by the long running nodes i.e. mining pools and thus never got mined. This is not really a big deal for mainnet since we do not expect half of the network to go down there but happens quite often on testnet. This patch lifts the restriction to some higher (and a bit unrealistic for normal use case but still safe in terms of DoS) value.