What changed, and why it matters
This commit fixes a single-word typo in a log message. The phrase 'on non-prune mode' was corrected to 'in non-prune mode'. It has no effect on program behavior, security, or user data.
Recommended action
No action needed; this is a documentation/typo-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
A one-character change in src/init.cpp replaces the preposition in a LogInfo() string from ‘on non-prune mode’ to ‘in non-prune mode’. The surrounding logic and service flag assignment are unchanged.
Changed components
src/init.cppInspect captured patch +1 / −1
diff --git a/src/init.cpp b/src/init.cpp
index d1c6a5ca..da1b927d 100644
--- a/src/init.cpp
+++ b/src/init.cpp
@@ -1872,7 +1872,7 @@ bool AppInitMain(NodeContext& node, interfaces::BlockAndHeaderTipInfo* tip_info)
} else {
// Prior to setting NODE_NETWORK, check if we can provide historical blocks.
if (!WITH_LOCK(chainman.GetMutex(), return chainman.BackgroundSyncInProgress())) {
- LogInfo("Setting NODE_NETWORK on non-prune mode");
+ LogInfo("Setting NODE_NETWORK in non-prune mode");
g_local_services = ServiceFlags(g_local_services | NODE_NETWORK);
} else {
LogInfo("Running node in NODE_NETWORK_LIMITED mode until snapshot background sync completes");
Risk score
Our methodology →Why this scored 15/100
Human-validated context
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
No validated notes yet.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.