patches Blockstore::is_shred_duplicate for resigned chained Merkle shreds#1271
Conversation
…reds With chained Merkle shreds which are signed by the retransmitter, different retransmitter signatures does not make a shred duplicate.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1271 +/- ##
=========================================
- Coverage 82.1% 82.1% -0.1%
=========================================
Files 893 893
Lines 236936 237008 +72
=========================================
+ Hits 194705 194717 +12
- Misses 42231 42291 +60 |
That is one possibility but also with 32:32 erasure encoding you can recover the whole batch as soon as you receive half of the batch. But at least some of the shreds you have already recovered from erasure encoding will be received from turbine later on as well. |
|
got it, so the retransmitter signature is not erasure coded, and recovered shreds will be missing the signature causing this duplicate check to fail when the shred is received through turbine |
right |
Problem
With chained Merkle shreds which are signed by the retransmitter, different retransmitter signatures does not make a shred duplicate.
Summary of Changes
patched Blockstore::is_shred_duplicate for resigned chained Merkle shreds