What changed, and why it matters
This commit only changes the wording of a log message produced when Bitcoin Core's database verification tool finishes. It does not alter security behavior, fix a bug, or change any code logic. The new message simply reports how many blocks were checked and at what verification level, and only claims 'no inconsistencies' when an appropriate deep check was actually performed.
No security action needed. This is a cosmetic/logging clarity change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch modifies the final LogInfo() output in CVerifyDB::VerifyDB(). Previously it always printed ‘No coin database inconsistencies in last N blocks (M transactions)’. Now it prints ‘checked last N blocks at level L’, and only adds ‘no coin database inconsistencies (M transactions)’ when nCheckLevel >= 3 and skipped_l3_checks is false. The existing return value logic for skipped_l3_checks is unchanged. No validation, state, or consensus code is affected.
Changed components
src/validation.cpp logging output in CVerifyDB::VerifyDB()Inspect captured patch +4 / −1
diff --git a/src/validation.cpp b/src/validation.cpp
index f85a834f..14182b60 100644
--- a/src/validation.cpp
+++ b/src/validation.cpp
@@ -4726,7 +4726,10 @@ VerifyDBResult CVerifyDB::VerifyDB(
}
}
- LogInfo("Verification: No coin database inconsistencies in last %i blocks (%i transactions)", block_count, nGoodTransactions);
+ LogInfo("Verification: checked last %i blocks at level %i", block_count, nCheckLevel);
+ if (nCheckLevel >= 3 && !skipped_l3_checks) {
+ LogInfo("Verification: no coin database inconsistencies (%i transactions)", nGoodTransactions);
+ }
if (skipped_l3_checks) {
return VerifyDBResult::SKIPPED_L3_CHECKS;
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.