aboutsummaryrefslogtreecommitdiff
path: root/src/net_processing.cpp
diff options
context:
space:
mode:
authorAmiti Uttarwar <amiti@uttarwar.org>2021-03-08 18:17:48 -0800
committerAmiti Uttarwar <amiti@uttarwar.org>2021-03-08 18:17:48 -0800
commitebde946a527e50630df180c6565ea5bf8d2ab5aa (patch)
treecedd2dbbea97998a6752209a95c89641c2f72ebf /src/net_processing.cpp
parenta8b0892b743bf5b0bd7192f801fbc6144320052b (diff)
downloadbitcoin-ebde946a527e50630df180c6565ea5bf8d2ab5aa.tar.xz
[doc] Improve comment about protected peers
The comment currently suggests a long-standing node would infrequently protect peers under normal circumstances. Clarify that we also protect peers that are synced to the same work as our chain tip.
Diffstat (limited to 'src/net_processing.cpp')
-rw-r--r--src/net_processing.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/net_processing.cpp b/src/net_processing.cpp
index d19e11f7b1..52e831ae1c 100644
--- a/src/net_processing.cpp
+++ b/src/net_processing.cpp
@@ -541,7 +541,7 @@ struct CNodeState {
* - its connection type is IsBlockOnlyConn() == false
* - it gave us a valid connecting header
* - we haven't reached MAX_OUTBOUND_PEERS_TO_PROTECT_FROM_DISCONNECT yet
- * - it has a better chain than we have
+ * - its chain tip has at least as much work as ours
*
* CHAIN_SYNC_TIMEOUT: if a peer's best known block has less work than our tip,
* set a timeout CHAIN_SYNC_TIMEOUT seconds in the future: