Bitcoin Core

This commit fixes the order in which a Bitcoin Core wallet reads startup settings. Previously, the `-keypool` setting (which controls how many spare Bitcoin addresses the wallet keeps ready) was read after the wallet had already loaded data from its database. The change moves all argument parsing, including `-keypool`, to happen before the database is loaded so the correct keypool size is available during wallet initialization. If the wrong size is used, the wallet might not generate or top up the expected number of addresses, which could affect backups and address availability.

This commit fixes a minor wallet logging bug. When creating an encrypted wallet, the keypool size was incorrectly reported as 0 in the logs because statistics were logged before the encryption keys were generated. The fix moves the logging to after wallet creation is fully complete and also updates a user-facing status message from 'Loading wallet…' to 'Creating wallet…' for accuracy. There is no security vulnerability here—only a cosmetic/logging correction.

This is a small, safe code cleanup in Bitcoin Core's wallet database code. It moves the logic that writes the wallet's version marker into its own reusable function, with no change to what data is actually written. There is no security issue here.

This is a code cleanup change that moves wallet command-line argument parsing into a separate helper function. It does not change what arguments are accepted, how they are validated, or any wallet behavior. There is no security issue visible in the change.

This commit is a code-quality and fuzz-testing efficiency change. It refactors how Bitcoin Core's fuzz tests skip descriptor inputs that are too computationally expensive to process, combining several checks into one helper function and adding a new leaf-size check. It does not change production wallet or node behavior, and there is no indication it fixes a security vulnerability in live software.

This commit adds a new internal helper called LineReader for parsing text lines from network data buffers. It is a clean, defensive implementation with length limits and explicit error handling. There is no indication it fixes a security bug or introduces a vulnerability.

This commit adds a new helper function that converts a timestamp into the RFC1123 date format used in HTTP headers. It is purely additive: it introduces a formatting routine and unit tests, with no changes to existing behavior or network-facing code. There is no security issue visible in the change itself.

This commit adds two small helper tools for comparing text strings in a case-insensitive way, intended for use when handling HTTP headers. It only introduces the helpers and their unit tests; it does not change any live network or wallet code. There is no security issue visible in the change itself.

This commit adds an optional new feature to a string-to-number helper so it can understand hexadecimal (base-16) input. It does not change existing behavior unless callers explicitly request base 16, and there is no indication it fixes a security bug or introduces a vulnerability.

This commit is a minor code cleanup in Bitcoin Core's networking code. It replaces an old-style C cast with a modern C++ reinterpret_cast and renames a few local variables. There is no functional change and no security issue.

This commit removes one line from a test file. It deletes an entry for 'UNKNOWN_ERROR' from a list of script error descriptions used only in unit tests. There is no change to the actual Bitcoin network code, consensus rules, or wallet behavior. It is a test-only cleanup with no security relevance visible in the commit.

This commit is a small cleanup in how Bitcoin reports script errors. It makes the software return a specific 'script number' error code when a transaction script tries to use an oversized or non-minimally encoded number, instead of the generic 'unknown error' it used before. The scripts still fail exactly as they did; only the error label changed. There is no indication this fixes a security vulnerability or changes consensus behavior.

This commit adds a new, more descriptive error code for problems with numbers inside Bitcoin's script language. Previously, these problems were reported as a generic 'unknown error.' The change only defines the new error label and its human-readable message; it does not yet change any code that actually raises the error. By itself, this is a small cleanup that does not fix or introduce a security vulnerability.

This commit adds new public programming interfaces (APIs) for the Bitcoin Core 'kernel' library so external programs can create, inspect, and validate block headers without downloading full blocks. It is a feature addition, not a fix for a known security bug. The code follows the existing patterns for memory handles and validation, and includes tests. There is no evidence in the commit or supplied references that this resolves a security vulnerability.

This commit only changes a code comment in a header file. It deletes an outdated, incorrect description of the removeUnchecked function and replaces it with a short, accurate note. No program logic, behavior, or security boundary is changed.

This commit fixes a test case in Bitcoin Core's own test suite. It changes a P2PK (pay-to-pubkey) script test so that it actually enables the P2SH validation flag it claims to be testing. The bug was only in the test data and test code, not in the production Bitcoin consensus or networking code. There is no change to how real Bitcoin transactions are validated.

This is a tiny test-only change that renames a wallet used in a single functional test to avoid intermittent failures on Windows. It does not change any production code, network behavior, or wallet security logic.

This is a follow-up cleanup commit that only touches benchmark and test files. It rewrites a loop for readability and adds explanatory comments about why a test uses an odd number of leaves and how the coinbase witness hash is initialized. No production code is changed, so there is no security impact.

This is a test-only change for Bitcoin Core's internal Python test framework. It fixes a port-conflict problem that could occur when running automated tests on FreeBSD, by making sure randomly chosen network ports for test P2P listeners come from a range that does not clash with the test framework's hard-coded ports. It does not affect the Bitcoin Core software that users run, does not change consensus or networking behavior, and has no security relevance for live Bitcoin nodes.

This commit only changes Bitcoin Core's internal test framework. It makes the network cleanup timeout scale with a test-configurable slowdown factor, so slow test environments don't falsely fail. There is no change to production Bitcoin node code, no user-facing behavior, and no security issue.

This commit is a routine internal API refactor for Bitcoin Core's experimental libbitcoinkernel C API. It adds create/copy/destroy functions for a block-validation state object and splits a C++ wrapper class into a read-only 'View' and an owning 'Handle'. There is no security fix, no bug fix, and no externally reported issue. It simply lets outside code allocate and own these state objects.

This commit only fixes a typo in a documentation comment. The code examples inside the comment had an extra 'return {' that made them syntactically invalid. No actual program code was changed, so there is no security effect.

This commit only changes the order of two checks inside a Bitcoin Core test helper. It makes no functional change to the Bitcoin software itself, does not affect live code, and has no security relevance. The change is intended to make debugging test failures easier by showing the error message before the error code in failure logs.

This is a minor cleanup of a single test file. It removes four temporary variables that stored transaction IDs and replaces their uses with direct property access. There is no change to Bitcoin Core's actual network or wallet behavior, and no security relevance.

This commit is a routine cleanup of Bitcoin Core's test code. It replaces a small helper class used to create test transactions with a standalone function and updates the tests that use it. There is no change to the live Bitcoin network code, no fix for a security bug, and no new security feature.