Bitcoin Core

This commit is a straightforward internal code cleanup in Bitcoin Core's logging system. It replaces a function that modified a string by repeatedly inserting text at the front with a function that builds the same string left-to-right and returns it. There is no security-relevant change here.

This commit only adds documentation comments to a header file. It explains which integer types the Bitcoin Kernel C API uses for different kinds of values. No code behavior was changed.

This commit only changes a single test file (interface_http.py) in Bitcoin Core. It refactors the test to use one node instead of three, switches some encodings from utf-8 to ascii, makes tests independent, and updates expected HTTP error codes from 400 to 413 for oversized requests. There is no change to production code, no security fix, and no vulnerability being introduced.

This commit is a minor type-cleanup change in Bitcoin Core's internal kernel API. It changes several height-related function parameters and return values from the generic `int` type to the explicitly-sized `int32_t` type. There is no security-relevant behavior change, no bug fix, and no disclosed vulnerability.

This commit adds a new public function to the Bitcoin Core library API that lets callers efficiently look up any ancestor block of a given block by its height. It is a pure feature addition with no security-relevant changes to existing behavior. There is no bug fix, no vulnerability disclosure, and no indication of a security issue.

This commit is a straightforward internal code cleanup in Bitcoin Core's logging system. It bundles log details (timestamp, thread name, message, category, etc.) into a single struct called log::Entry and passes that struct around instead of many separate arguments. There is no security fix or behavior change visible in the diff.

This commit adds two pieces of metadata to each log entry: the time it was created and the name of the thread that created it. It is a straightforward internal logging improvement with no apparent security relevance.

This is a minor code-quality change that adds the C++ keyword 'explicit' to a constructor. It prevents the compiler from silently converting other types into a SourceLocation object, following a common C++ best-practice guideline. There is no security bug being fixed here.

This commit removes an extra linker flag (-lstdc++) from a Bitcoin Core continuous integration (CI) script used only for a memory-sanitizer fuzz-testing build. It is a build-configuration cleanup, not a code change affecting the Bitcoin software users run. There is no security-relevant change to the project's runtime behavior or to shipped binaries.

This commit simply updates the version of the LLVM compiler toolchain used in automated testing from 22.1.0 to 22.1.3. It is a routine maintenance change to the project's continuous integration (CI) setup and does not alter Bitcoin Core's actual code or how it runs for users.

This commit fixes four minor typos and spacing issues in documentation files only. There are no code changes and no security implications.

This commit is a minor cleanup of a Bitcoin Core functional test file. It moves some connection-checking code into a helper method so it is reused by multiple tests, rather than being duplicated in each test. There is no change to the actual Bitcoin Core software that users run, and no security issue is introduced or fixed.

This change adds a safety check while reading old Berkeley DB (BDB) wallet files during migration. It verifies that each page in the database's tree structure is at the expected depth level, which prevents malformed or attacker-crafted files from causing infinite loops or confusion during wallet import. The patch is defensive hardening rather than a fix for an active exploit, and it includes a new fuzz-test error path so the security check can be automatically exercised.

This patch fixes a bug in Bitcoin Core's wallet migration code that reads old Berkeley DB wallet files. A malformed wallet file could claim an overflow data record was extremely long, causing the software to loop through pages forever. The fix checks that the claimed length fits within the actual file size and stops reading if the collected data exceeds that claimed length. This prevents a denial-of-service via infinite loop when opening a crafted wallet file.

This is a test-only code cleanup. It changes how test scripts call a helper function named create_block so that the timestamp argument must be passed by its keyword name (ntime=...) rather than as a plain positional number. This makes the tests easier to read and prevents developers from accidentally swapping the height and timestamp arguments, but it does not change Bitcoin Core's production code or network behavior at all.

This commit only removes unused 'create_coinbase' import statements from 17 Bitcoin Core test files. It is a routine code cleanup with no effect on the actual Bitcoin node software or its security.

This commit is a purely mechanical update to Bitcoin Core's internal test suite. It changes how test scripts call a helper function named create_block, switching from passing a pre-built coinbase transaction to passing just the block height and letting the helper build the coinbase internally. No production code, consensus rules, or network behavior are modified. There is no security relevance.

This is a harmless test-framework cleanup. It lets Bitcoin Core's internal test helper create_block accept a block height directly, instead of forcing test writers to manually build a coinbase transaction first. It only touches test code and adds a unit test for the new convenience option.

This commit adds a new command-line option `-rpcid` to bitcoin-cli that lets users set their own identifier on JSON-RPC requests, and includes that identifier in server debug logs. It is a usability/debugging feature with no security relevance visible in the code or commit message.

This commit only adds a new release-notes document for Bitcoin Core version 31.0. It contains no code changes, no configuration changes, and no bug fixes. It is purely documentation summarizing features and changes already present in the release.

This is a minor test-only fix. It makes a Bitcoin Core functional test respect the configurable timeout factor when waiting for a helper tool to respond, and makes two function arguments require explicit names. It does not change the actual Bitcoin node software or introduce any security issue.

This commit removes one source file from the build list for the bitcoinkernel library because that file is not actually used by anything in that library. It is a routine cleanup change with no security relevance.

This commit tightens a test-only C++ concept so that any `ToBytes()` method must return something convertible to a byte span. It is purely a test-code quality improvement and does not change production behavior or fix a security bug.

This commit adds a new public library function that converts a Bitcoin block header into its standard 80-byte wire format. It is a straightforward feature addition with no visible bug fix or security change. The code uses safe, fixed-size buffers and existing well-tested serialization routines.

This commit adds a new helper class called SpanWriter that lets Bitcoin Core write serialized data into a fixed-size byte buffer without allocating new memory. It includes bounds checking so writing past the end throws an error, and it comes with unit tests. There is no indication this is a security fix or that it addresses any reported vulnerability.