Handle chained_merkle_conflict_duplicate_proofs

Author: InKryption

src/shred_network/collector/duplicate_shred_handler.zig

@@ -23,6 +23,7 @@ const MAX_DUPLICATE_SHREDS: usize = sig.gossip.data.MAX_DUPLICATE_SHREDS;
 pub const DuplicateShredHandler = struct {
     ledger_reader: sig.ledger.Reader,
     result_writer: sig.ledger.ResultWriter,
+    epoch_tracker: *const sig.core.EpochTracker,
     duplicate_slots_sender: ?*Channel(Slot),
     push_msg_queue_mux: ?*sig.gossip.GossipService.PushMessageQueue,
     keypair: *const KeyPair,
@@ -84,9 +85,17 @@ pub const DuplicateShredHandler = struct {
                 .ChainedMerkleRootConflict => |conflict| {
                     const shred_slot = conflict.original.commonHeader().slot;
 
-                    // 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;
+                    const chained_merkle_conflict_duplicate_proofs: bool = feature: {
+                        const epoch_info = self.epoch_tracker.getEpochInfo(shred_slot) catch
+                            break :feature false;
+                        const feature_slot = epoch_info.feature_set.get(
+                            .chained_merkle_conflict_duplicate_proofs,
+                        ) orelse break :feature false;
+                        const feat_epoch = self.epoch_tracker.epoch_schedule.getEpoch(feature_slot);
+                        const shred_epoch = self.epoch_tracker.epoch_schedule.getEpoch(shred_slot);
+                        break :feature feat_epoch < shred_epoch;
+                    };
+                    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