feat: enhance error handling for invalid checksums

Improved logging and proactive disconnection for peers sending messages with invalid checksums. This change ensures that potential message corruption is addressed promptly, enhancing network stability.

Author: PastaPastaPasta

dash-spv/src/network/connection.rs

@@ -461,17 +461,24 @@ impl TcpConnection {
                 expected,
                 actual,
             }) => {
-                // Special handling for checksum errors - skip the message and return empty queue
-                tracing::warn!("Skipping message with invalid checksum from {}: expected {:02x?}, actual {:02x?}", 
-                              self.address, expected, actual);
+                // Extra logging and proactively disconnect on checksum mismatches
+                tracing::warn!(
+                    "Invalid checksum from {}: expected {:02x?}, actual {:02x?} — disconnecting peer",
+                    self.address,
+                    expected,
+                    actual
+                );
 
                 // Check if this looks like a version message corruption by checking for all-zeros checksum
                 if actual == [0, 0, 0, 0] {
-                    tracing::warn!("All-zeros checksum detected from {}, likely corrupted version message - skipping", self.address);
+                    tracing::warn!(
+                        "All-zeros checksum from {} indicates likely corrupted stream/version message — disconnecting",
+                        self.address
+                    );
                 }
 
-                // Return empty queue instead of failing the connection
-                Ok(None)
+                // Treat as peer disconnect so upper layers drop and reconnect
+                Err(NetworkError::PeerDisconnected)
             }
             Err(e) => {
                 tracing::error!("Failed to decode message from {}: {}", self.address, e);