From 55390d1827c724b8c09ac9ffa4b97fccb370b322 Mon Sep 17 00:00:00 2001
From: Hodlinator <172445034+hodlinator@users.noreply.github.com>
Date: Mon, 31 Aug 2026 21:29:31 +0200
Subject: [PATCH] doc: Correct comment about which subsystem detects lagging
 clocks

---
 src/net_processing.cpp | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/net_processing.cpp b/src/net_processing.cpp
index c0a7c34c465..34a892a8ac2 100644
--- a/src/net_processing.cpp
+++ b/src/net_processing.cpp
@@ -3034,10 +3034,10 @@ bool PeerManagerImpl::TryLowWorkHeadersSync(Peer& peer, CNode& pfrom, const CBlo
                 peer.m_headers_sync.reset(new HeadersSyncState(peer.m_id, m_chainparams.GetConsensus(),
                     m_chainparams.HeadersSync(), chain_start_header, minimum_chain_work));
             } catch (const HeadersSyncState::SystemClockError& e) {
-                // Typically we would expect the chain state loading logic to
-                // already have verified that the tip of the locally stored
-                // chain is <= system clock + MAX_FUTURE_BLOCK_TIME. Getting
-                // here is really unexpected.
+                // The chain state loading logic performs an earlier check to
+                // verify that the tip of the locally stored chain is <=
+                // system clock + MAX_FUTURE_BLOCK_TIME.
+                // But if we have no pre-existing chain state we might get here.
                 const auto msg{strprintf("Failure when attempting to initiate headers sync: %s", e.what())};
                 std::cerr << msg << std::endl;
                 LogError("%s", msg);