This commit only edits changelog Markdown files. It documents that several prior releases were yanked from crates.io because their required Rust version was raised too aggressively, and it adds notes about newer replacement releases. There…
This commit is a small code-quality refactor in Bitcoin Core. It changes several UTXO-statistics helpers so they take a database view by reference instead of by pointer. That removes the possibility of passing a null pointer and makes the …
API hardening: pointer-to-reference conversion removes a nullability contractNo memory-safety bug demonstrated in the diffNo consensus, P2P, wallet, or RPC semantic changes visible
This is a small cleanup change in Bitcoin Core that removes leftover null checks after a previous refactor made database cursors always return a valid object. There is no security issue in the diff itself.
This commit is a routine code cleanup. It removes an unused cursor-iteration method from the base coin-view interface and its empty/forwarding/throwing implementations, keeping the method only on the concrete database class that actually s…
This is a small internal code cleanup in Bitcoin Core. It changes several functions that compute UTXO (unspent transaction output) statistics so they accept a more specific database-view pointer instead of a generic one, because only the c…
This commit is just a documentation update adding a release note for a previously fixed bug. The actual bug was a crash (panic) in LND's DNS fallback code: when looking up network routing information, the program assumed every answer from …
Denial of Service (daemon panic/crash) via DNS response manipulationUnsafe type assertion in DNS SRV lookup pathOut-of-bounds index access on empty LookupHost result
This commit only removes a sentence from the release notes document for version 0.22.0. It does not change any program code, so it cannot by itself introduce, fix, or alter a security vulnerability. The deleted text described a previously …
This commit is mostly a cleanup patch: it wraps long lines caused by a recent library rename and, importantly, adds a missing error check around a call that loads a Bitcoin transaction filter. The error check prevents a silent failure wher…
Previously unchecked error return now handledSilent failure in transaction filter update could lead to stale chain viewNo input validation, memory safety, or cryptographic changes present
This commit adds a new feature to the COLDCARD hardware wallet that lets users apply the text of a Secure Note or the value of a Secure Note password as their BIP-39 wallet passphrase. It also tightens how printable ASCII is checked in a f…
New feature exposes stored Secure Notes / Passwords as BIP-39 passphrasesInput validation relies on length, printable-ASCII, and rstrip of trailing whitespace/tab/newlineRefactored text sanitization changes control-flow for message signing and PSBT message warnings
This is a large dependency upgrade for the LND Lightning node software. It moves LND from older btcd Bitcoin library packages to new 'v2' packages and updates related wallet and network libraries. The commit is almost entirely mechanical i…
Large dependency upgrade touching core Bitcoin primitives (wire, txscript, chainhash, btcutil, psbt, address)Migration to new v2 module layout with API changes in address handlingPins new upstream releases (btcd 0.26.0, btcwallet 0.17.0, neutrino 0.18.0, lightning-onion 1.4.0) that may include undisclosed fixes
This commit fixes a bug in the COLDCARD Q1 hardware wallet where displaying certain QR codes containing non-English or special characters could cause the device to crash with an assertion failure. The fix ensures text is converted to UTF-8…
Assertion failure/crash in QR display pathLength mismatch between codepoints and UTF-8 bytesDenial-of-service-like symptom (device crash on user data display)
This commit adds a new feature to the COLDCARD firmware that lets users organize their saved secure notes and passwords into groups, similar to folders. It is a user-experience improvement and does not fix or introduce any security vulnera…
A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.