Skip to content
This repository was archived by the owner on Jan 22, 2025. It is now read-only.

Conversation

@AshwinSekar
Copy link
Contributor

@AshwinSekar AshwinSekar commented Aug 17, 2023

Problem

Duplicate shreds detected due to invalid LAST_SHRED_IN_SLOT flags, or erasure metas are stored in blockstore but never forwarded to the cluster or the state machine.

Similarly duplicate shreds received through gossip are never forwarded to the state machine.

Also on replay from ledger, we do not do anything with the blockstore cf indicating duplicate proof, this should be sent to the state machine.

Summary of Changes

Fix the plumbing.

Fixes #

@AshwinSekar AshwinSekar force-pushed the duplicate-shred-proof branch 3 times, most recently from 22600b5 to 6c94e92 Compare August 17, 2023 20:27
@t-nelson
Copy link
Contributor

this is kinda large to review. description implies that there may be an opportunity to split it into (at least) three isolated PRs. possible?

@AshwinSekar
Copy link
Contributor Author

will split this up as suggested.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants