fix: handle reorg in epoch 3.0

components/stacks-network/src/chains_coordinator.rs

@@ -392,17 +392,10 @@ pub async fn start_chains_coordinator(
                         unreachable!() // TODO(lgalabru): good enough for now - code path unreachable in the context of Devnet
                     }
                     StacksChainEvent::ChainUpdatedWithReorg(data) => {
-                        // looks like in nakamoto we have reorgs, lets try that
-                        let block_id = data
-                            .blocks_to_apply
-                            .last()
-                            .unwrap()
-                            .block
-                            .block_identifier
-                            .index;
-                        let reorg_data = format!("{:#?}", data);
-                        std::fs::write(format!("reorgdata-{block_id}.txt"), reorg_data)
-                            .expect("Failed to write reorg data to file");
+                        // reorgs should not happen in devnet
+                        // tests showed that it can happen in epoch 3.0 but should not
+                        // this patch allows to handle it, but further investigation will be done
+                        // with blockchain team in order to avoid this
                         devnet_event_tx
                             .send(DevnetEvent::warning("Stacks reorg received".to_string()))
                             .expect("Unable to send reorg event");