Fix peer's status stale information should not appear too early.

Author: cheatfate

beacon_chain/sync/sync_overseer2.nim

@@ -37,6 +37,8 @@ const
     ## Number of requests performed by single peer in one syncing step
   RepeatingFailuresCount* = 2
     ## Number of repeating errors before starting rewind process.
+  StatusStalePeriod* = 5
+    ## Number of slots before peer's status information could be stale.
 
 func shortLog(optblkid: Opt[BlockId]): string =
   if optblkid.isNone():
@@ -1102,6 +1104,7 @@ proc doPeerUpdateStatus(
     peer: Peer
 ): Future[bool] {.async: (raises: [CancelledError]).} =
   let
+    dag = overseer.consensusManager.dag
     peerHead = peer.getHeadBlockId()
     peerFinalizedCheckpoint = peer.getFinalizedCheckpoint()
     peerStatusAge = Moment.now() - peer.getStatusLastTime()
@@ -1129,8 +1132,11 @@ proc doPeerUpdateStatus(
     newPeerHead = peer.getHeadBlockId()
 
   if peerHead.slot >= newPeerHead.slot:
-    peer.updateScore(PeerScoreStaleStatus)
-    debug "Peer's status information is stale"
+    let stalePeriod =
+      (dag.cfg.timeParams.SLOT_DURATION * StatusStalePeriod)
+    if peerStatusAge >= stalePeriod:
+      peer.updateScore(PeerScoreStaleStatus)
+      debug "Peer's status information is stale"
   else:
     # Updating data structures about newly received Peer's status information.
     overseer.updatePeer(peer)