This commit only updates an automatically generated API listing file. It reflects a change in how an error type is declared in the source code (from a public enum to a public struct wrapper), but the commit itself does not contain any actu…
This commit is a routine API design change, not a security fix. It renames an internal error enum and wraps it in a private struct so the library can keep the error type flexible before its first stable release. No vulnerability is patched…
No security-relevant keywords in commit title or messageNo bounds checks, input validation, or cryptographic logic changedNo memory-safety, panic, or unsafe-code modifications
This is a routine performance refactor. It swaps a slow, character-by-character hex formatting loop for one that writes whole chunks at a time. There is no security-relevant change.
This commit adds a small, harmless feature to a Rust Bitcoin encoding library. It lets an optional encoder report its length when it has a value, and report zero length when it is empty. There is no security issue here.
This commit adds a new automated test (a fuzzing harness) for Bitcoin Core's coin database view. It does not change any production code, user-facing behavior, or network protocol. It only adds a test that exercises reading the LevelDB-back…
This commit only adds a release note describing a performance improvement for block validation. It contains no code changes, no bug fixes, and no security-related content.
This is a preparatory code change for future multi-threaded coin fetching in Bitcoin Core. It adds a synchronization flag (std::atomic_flag) around a shared data field so that worker threads can safely signal when they have finished writin…
Concurrency synchronization added for shared coin fieldUse of release/acquire atomic semantics to prevent data racesPreparation for multi-threaded ProcessInput execution
This commit changes how Bitcoin Core fetches transaction input data (the 'coins' spent by transactions in a block). Instead of doing all lookups one-by-one on the main thread, it now submits the work to a thread pool. The change is describ…
New concurrent shared state (m_inputs, m_input_head, m_input_tail, m_futures) across multiple worker threads and the main threadFallback path on thread-pool submission failure clears shared state and logs a warningAddition of destructor and Flush override that must correctly synchronize with running workers
This commit only updates a code comment (docstring) in a header file. It explains how a new parallel coin-fetching mechanism works. No actual code logic was changed, so it cannot introduce or fix a security vulnerability on its own.
This commit only adds and updates unit tests for an existing Bitcoin Core component called CoinsViewOverlay. It does not change any production code that runs on the live Bitcoin network, so it cannot directly introduce a security vulnerabi…
This commit only changes Bitcoin Core's internal fuzz tests—specialized randomized test programs used during development to catch bugs. It adds test coverage for a new caching helper called CoinsViewOverlay::StartFetching. There is no chan…
No production code changesOnly fuzz-test harnesses modifiedAdded test coverage for CoinsViewOverlay::StartFetching
This commit is a performance optimization for Bitcoin Core's block validation. It pre-fetches the previous transaction outputs (the 'coins' being spent) for all inputs in a block before the main validation work begins, and it does so in pa…
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.