Reduce AwaitReply timeout from 5 minutes to 90 seconds

90s is ~4.5x the expected mainnet block interval (20s average),
providing sufficient margin while detecting dead connections faster.

Author: michaeljfazio

crates/torsten-network/src/pipelined.rs

@@ -250,17 +250,18 @@ impl PipelinedPeerClient {
                     // After AwaitReply, the server enters MustReply state and
                     // will send RollForward/RollBackward when a block arrives.
                     // We wait for that response with a timeout — if no block
-                    // arrives within 5 minutes, the connection is likely dead
-                    // (e.g., after machine sleep/hibernate).
-                    const AWAIT_REPLY_TIMEOUT: Duration = Duration::from_secs(300);
+                    // arrives within 90 seconds, the connection is likely dead
+                    // (e.g., after machine sleep/hibernate). 90s is ~4.5x the
+                    // expected mainnet block interval (20s average).
+                    const AWAIT_REPLY_TIMEOUT: Duration = Duration::from_secs(90);
                     let wait_response: Message<HeaderContent> = tokio::time::timeout(
                         AWAIT_REPLY_TIMEOUT,
                         self.cs_buf.recv_full_msg(),
                     )
                     .await
                     .map_err(|_| {
                         ClientError::ChainSync(
-                            "AwaitReply timeout: no block received in 5 minutes, \
+                            "AwaitReply timeout: no block received in 90 seconds, \
                              connection may be stale"
                                 .into(),
                         )