eth/catalyst: allow duplicate blob hashes #31788
Merged
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.
While running kurtosis and spamoor, I noticed occasional
null
entries coming back fromgetBlobsV2
. After investigating, I found that spamoor can use the same blob data across multiple transactions, so with larger blob counts, there's an increased chance that a blob is included in a block more than once. As a result, previous indexes in the hash-to-index map ingetBlobsV2
would get overwritten.I changed the map from
map[common.Hash]int
tomap[common.Hash][]int
to handle this case. I decided to go this route because it's the smallest-possible fix, but it could also make sense to updateblobpool.GetBlobs
to de-duplicate the hashes.