Revert "Reduce duplicate peer traffic for ledger data (#5126)" #5300
+143
−1,013
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.
High Level Overview of Change
This reverts commit dd5e655. It has introduced a regression causing slow close times and syncing issues. A fix will be attempted later.
Context of Change
#5126 introduced duplicate message checking and suppression. The absence of those messages may explain the symptoms that are being seen on test networks.
Type of Change
API Impact
None
Before / After
Reverses the changes from #5126. The full set of changes does not necessarily have to be reviewed. It may be sufficient to verify that the code is what it would have been without that commit.
Future Tasks
Find and fix the actual bug. I have a feeling it's related to the message hashing.