Merge pull request #10102 from yyforyongyu/fix-UpdatesInHorizon

Catch bad gossip peer and fix `UpdatesInHorizon`

sample-lnd.conf

@@ -1797,6 +1797,23 @@
 ; See docs/gossip_rate_limiting.md for mor information.
 ; gossip.filter-concurrency=5
 
+; The score at which a peer is banned. Each time a peer sends a gossip message
+; that is considered invalid, its ban score is incremented. Once the score
+; reaches this threshold, the peer is banned for a default of 48 hours, and we
+; will no longer process gossip messages from them. This is a measure to
+; protect the node from spam and misbehaving peers. Setting this value to 0
+; disables banning completely.
+;
+; A gossip message can be considered invalid for several reasons, including:
+; - Invalid signature on the announcement.
+; - Stale timestamp, older than what we already have.
+; - Too many channel updates for the same channel in a short period.
+; - Announcing a channel that is not found on-chain.
+; - Announcing a channel that has already been closed.
+; - Announcing a channel with an invalid proof.
+;
+; gossip.ban-threshold=100
+
 [invoices]
 
 ; If a hold invoice has accepted htlcs that reach their expiry height and are