What changed, and why it matters
This commit fixes a typo in a log message only: 'alloacting' is corrected to 'allocating'. There is no functional code change, no security fix, and no behavior change.
Recommended action
No security action needed. Treat as a normal non-functional cleanup commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff changes a single string inside a log.Infof call in blockchain/utxocache.go. The surrounding logic, memory calculation, and all other code remain identical. It is purely a spelling correction in a user-visible log string.
Changed components
blockchain/utxocache.goInspect captured patch +1 / −1
diff --git a/blockchain/utxocache.go b/blockchain/utxocache.go
index 550d8c5..5e260b6 100644
--- a/blockchain/utxocache.go
+++ b/blockchain/utxocache.go
@@ -234,7 +234,7 @@ func newUtxoCache(db database.DB, maxTotalMemoryUsage uint64) *utxoCache {
numMaxElements := calculateMinEntries(int(maxTotalMemoryUsage), bucketSize+avgEntrySize)
numMaxElements -= 1
- log.Infof("Pre-alloacting for %d MiB", maxTotalMemoryUsage/(1024*1024)+1)
+ log.Infof("Pre-allocating for %d MiB", maxTotalMemoryUsage/(1024*1024)+1)
m := make(map[wire.OutPoint]*UtxoEntry, numMaxElements)
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.