Bitcoin Core

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.

This commit only changes a benchmark test file. It refines how the performance of a script verification test is measured so that setup work (clearing the stack) is not counted in the timing. There is no change to the Bitcoin Core software that users run, no change to consensus or validation rules, and no security issue.

This commit only adds a new performance benchmark to Bitcoin Core. It measures how long it takes to verify a specific kind of Taproot transaction (a P2TR script-path spend) and makes minor cleanups to existing benchmark code. It does not change any production wallet, consensus, or networking code, so it cannot directly affect user funds or network security.

This is a test-only change to the SOCKS5 server helper used in Bitcoin Core's functional tests. It makes the test server shut down its background connection-handler threads cleanly instead of leaving them running. It does not affect the Bitcoin Core node software that users run on the network, so it has no direct security impact on live Bitcoin operations.

This commit changes a single line in a GitHub Actions CI workflow file. It renames the cache key used for storing pre-built vcpkg dependency packages so that the CI system will rebuild them from scratch instead of reusing the old cached versions. This is a routine build-infrastructure maintenance change with no apparent security relevance.

This commit is a straightforward internal cleanup: it changes how Bitcoin Core stores the moment a peer connected, switching from a coarse 'whole seconds since 1970' value to a richer clock type that can carry finer precision. The change touches many files but only rewrites type declarations and conversions; it does not alter network rules, consensus logic, or security behavior. There is no indication this fixes or introduces a vulnerability.

This commit fixes a spelling mistake in a developer documentation file, changing 'parlor' to 'parlance'. It does not change any program code, behavior, or security properties.

This is a small bug fix in a helper signet mining script. The script would crash with a NameError when it tried to log a warning about an unexpected previous block, because it referenced a variable that only existed in the calling function. The fix uses the correct variable that was already passed into the method. It is a straightforward coding mistake with no security exploit.

This commit is a routine optimization to Bitcoin Core's coin-selection algorithm. It makes the wallet skip more redundant combinations when choosing which coins to spend, slightly reducing the number of attempts the algorithm tries. There is no security issue here.

This commit is a pure performance optimization for Bitcoin Core's coin selection algorithm. It avoids re-evaluating equivalent combinations of coins when choosing which inputs to include in a transaction. There is no security vulnerability being fixed here.

This commit is a performance optimization to Bitcoin Core's coin-selection algorithm. It pre-computes a running total ('lookahead') of remaining coin values so the Branch-and-Bound search can skip dead-end branches faster. The change is purely algorithmic and does not appear to introduce or fix a security vulnerability. Test expectations are updated only to reflect fewer search attempts.

This commit is a performance optimization for Bitcoin Core's coin selection algorithm. It teaches the Branch-and-Bound (BnB) coin picker to skip exploring input combinations that are guaranteed to be worse at high transaction fees. It does not fix a security vulnerability, crash, or consensus bug. The change could theoretically affect which coins are selected for a transaction, but only in a way that is intended to preserve the existing best-choice behavior while doing less work.

This commit changes how Bitcoin Core's coin-selection algorithm tracks whether it finished its search. Previously, the code created the result object after the loop, so it could not record whether the Branch-and-Bound (BnB) search hit its iteration limit or completed the full search. The patch moves the result object earlier and marks it 'completed' or 'not completed' inside the loop. This is a correctness/observability improvement for fee estimation and coin-selection diagnostics, not a direct fix for a remote exploit. It could matter for security indirectly: if BnB aborts early, the wallet may fall back to a less optimal selection, possibly paying higher fees or creating larger change, but there is no evidence in the commit of a vulnerability being disclosed or exploited.