v1.18: gossip: do not allow duplicate proofs for incorrect shred versions (backport of #1931) #1940
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.
Problem
Nodes that do not participate in a cluster restart can have old shreds with a previous shred version.
Upon restart they will create duplicate proofs using this old shred version and newly received shreds and propagate them to the rest of the cluster.
Summary of Changes
Disallow creation and consumption of duplicate proofs involving shreds with incorrect shred versions
This is an automatic backport of pull request #1931 done by [Mergify](https://mergify.com).