Bitcoin Core

This commit only adds documentation. It explains what ASMap data is, how it is sourced and verified, and adds a checklist item to the release process reminding developers to update the embedded ASMap file before a release. No code, configuration, or data files were changed.

This commit changes one Bitcoin Core continuous integration (CI) test job to compile the software with the embedded asmap feature turned off. It does not change any production code, user-facing behavior, or network logic. It is purely a build/test configuration tweak to ensure that building without embedded asmap still works in CI.

This commit adds an optional feature that lets Bitcoin Core ship its IP-to-ASN mapping data built into the program binary, so users can enable it with a simple `-asmap` flag instead of downloading and pointing to a separate file. It is a feature addition, not a fix for an active security flaw. The change could have minor security implications if the embedded data were malformed or tampered with, but the code validates the data before use and fails startup if validation fails.

This commit is a routine build-system change. It makes Bitcoin Core automatically include a small network-mapping data file (ASMap) into the compiled binary by default, while adding an option to turn that embedding off. There is no indication this fixes or introduces a security vulnerability.

This commit adds a new binary data file containing an internet routing map (ASMap data) used by Bitcoin Core to group IP addresses by their network owner. It is a build/data-only change with no code modifications. There is no indication of a security vulnerability, bug fix, or malicious content in the commit itself.

This commit simply removes one automated testing job from Bitcoin Core's GitHub Actions continuous integration setup. It does not change any Bitcoin node, wallet, or network code. There is no security vulnerability introduced or fixed here.

This commit is a code cleanup inside a performance benchmark file. It changes how a test script creates a fake Bitcoin transaction and signature for timing purposes only. There is no change to the live Bitcoin network code, wallet handling, or consensus rules, and nothing in the commit suggests a security fix or vulnerability.

This commit is a minor logging cleanup. It changes one routine status message from a default 'info' log to a less-visible 'debug' log, and makes the log message show the full file path instead of just the filename. There is no security issue here.

This is a small internal code cleanup in Bitcoin Core's socket helper class. It changes how a temporary shared pointer is created so that it refers to an existing socket object without taking ownership of it. There is no user-facing behavior change and no security fix.

This commit removes a temporary workaround from Bitcoin Core's continuous integration (CI) test script. The workaround previously patched LevelDB source code during CI runs to avoid reading from uninitialized memory. The removal is cleanup after a LevelDB update made the workaround unnecessary. It is not a security fix and does not change any production code.

This commit pulls in a small LevelDB fix that initializes a file-size variable to zero before use. Without the fix, the variable could contain leftover/unpredictable data, which in C++ is called 'undefined behavior.' In practical terms this is most likely a stability/reliability fix rather than an exploitable Bitcoin security bug, because the value is later overwritten during normal database operations.

This is a minor internal change to Bitcoin Core's continuous integration (CI) shell script. It removes a one-line helper variable and directly runs a ccache version/statistics command, adding the --verbose flag to the statistics output. There is no user-facing change, no wallet or network code is touched, and no security issue is present.

This change fixes how Bitcoin Core counts key expressions when parsing Miniscript descriptors. Previously, the parser kept a private copy of a counter (m_offset), so updates inside the parser did not propagate back to the caller. By switching to a shared reference (m_expr_index), the caller's counter stays correct across nested or repeated Miniscript parsing. A wrong counter could lead to incorrect descriptor metadata, which in wallet software might cause addresses, derivation paths, or key identifiers to be mis-indexed. There is no direct remote exploit shown in the diff, but the bug could affect wallet correctness and user funds if a descriptor relying on the counter is used.

This change fixes how Bitcoin Core reads certain pieces of text inside Miniscript and descriptor expressions. Previously, the parser looked for the next closing parenthesis to decide where an argument ended. That simple scan broke when the argument itself contained nested parentheses, such as a musig(...) key expression inside pk(...). The new code uses proper expression-parsing helpers that understand matching parentheses, so nested structures are handled correctly. The commit message explicitly calls this a fix for parsing musig() inside pk(), pkh(), pk_k(), and pk_h().

This is a small internal code cleanup in Bitcoin Core's descriptor parser. It moves the counting of key expressions (used to label parsed public keys) into a helper function so callers don't have to do it manually. There is no visible change in behavior for users, no bug fix, and no security-relevant change.

This commit only adds new test cases for an existing Bitcoin wallet feature (MuSig multi-signature support inside miniscript expressions). It does not change production wallet logic, consensus rules, or network behavior. The changes are confined to a single functional test file and expand coverage for different miniscript patterns such as pkh and pk_h.

This commit adds new internal test-only checks to make sure Bitcoin Core's descriptor parser correctly counts key expressions. It does not change user-facing behavior or fix a known live bug; it is a regression test and small helper-code addition to verify an invariant (every key has a unique index and the count matches).

This commit only changes build instructions to add Boost header files as a dependency for two Bitcoin Core programs. It does not change any program logic, fix a bug, or alter how the software behaves at runtime. There is no security issue here.

This is a small code-quality cleanup in Bitcoin Core's wallet code. It changes how an internal notification signal is wired up so that it no longer relies on an obscure, undocumented feature of the Boost signals library. The change prevents a future risk that a Boost update could silently break wallet address notifications, but there is no known current bug or security vulnerability being exploited.

This commit only adds a code comment explaining why a particular function call is safe. It does not change any program logic, fix a bug, or alter validation behavior. There is no security issue here.

This commit only adds explanatory comments to a piece of Bitcoin Core's transaction-validation code. It does not change any behavior, fix a bug, or alter consensus rules. The comment documents why a particular error check is mathematically unreachable under the already-enforced preconditions, while leaving the check in place for safety.

This is a small internal code cleanup in Bitcoin Core's database wrapper. It replaces one temporary data-reading helper (DataStream) with another (SpanReader) and reuses an existing mutable buffer to avoid copying data during de-obfuscation. There is no visible security bug or behavior change in the diff.

This is a small code cleanup in Bitcoin Core's Qt wallet GUI. It replaces a two-step copy of a string into a byte vector with a direct reader that views the string's bytes without copying. There is no security issue visible in the change.

This is a small defensive code cleanup in Bitcoin Core. A function called SpanReader::ignore could previously call a standard-library span operation with an oversized offset, which is undefined behavior and, with hardening enabled, causes the program to crash. The fix adds a bounds check that throws a normal end-of-data exception instead. The commit message says this bad path was not reachable in practice, so the change is mainly about removing undefined behavior rather than fixing an exploitable bug.

This commit is a straightforward internal code reorganization for Bitcoin Core's logging system. It moves where log message formatting happens so that smaller parts of the code can include a lighter logging header. The commit itself notes a minor, non-security performance side effect in an unusual configuration, but there is no vulnerability or security fix here.