feat(consensus): Send duplicate slots from shred network to consensus (revival of #1027)#1172
feat(consensus): Send duplicate slots from shred network to consensus (revival of #1027)#1172InKryption wants to merge 23 commits intomainfrom
Conversation
920dcef to
5a16138
Compare
a974315 to
994f7c0
Compare
| // TODO: Check feature flag for chained_merkle_conflict_duplicate_proofs | ||
| // For now, we'll store it unconditionally. When feature checking is implemented, | ||
| // this should check: if (!chained_merkle_conflict_duplicate_proofs) continue; | ||
|
|
||
| // Although this proof can be immediately stored on detection, we wait until | ||
| // here in order to check the feature flag, as storage in ledger can | ||
| // preclude the detection of other duplicate proofs in this slot |
There was a problem hiding this comment.
Can we not pass the feature set and check it now?
There was a problem hiding this comment.
I've looked through it, and it's actually not entirely clear to me what the best way would be to pass the feature set through.
There was a problem hiding this comment.
What issue do you see with passing the feature set in? We could potentially add it to EpochInfo in the EpochTracker unless we move the slot tracker outside replay. While the feature set is constant for most of the duration of an epoch, it can be different across forks in an epoch until the first slot in said epoch is rooted. This could be addressed on top of epoch-state-tracking if required. Another thing to check is whether this feature is activated on all clusters. If it is, just add a note here and we can remove the check.
e1ffafe to
6ee04e6
Compare
e2a2b4d to
1e2810a
Compare
eccc9fb to
b6ca584
Compare
Drop dep on gossip table
Co-authored-by: Drew Nutter <dnut@users.noreply.github.com>
Co-authored-by: Drew Nutter <dnut@users.noreply.github.com>
b6ca584 to
500e989
Compare
No description provided.