Bitcoin Core

This commit fixes an integer overflow bug in Bitcoin Core's optional coin statistics index. The index keeps running totals of spent and created coins, and on long-running or high-activity networks these totals could exceed the range of the 64-bit 'CAmount' type, causing wrong statistics or node instability. The fix widens the at-risk totals to a 256-bit type and removes a redundant stored total that can be computed from other values. It also changes the index's database directory name so upgraded nodes do not reuse the old, buggy data, while leaving the old directory in place for users who might downgrade.

This commit changes Bitcoin Core's GitHub Actions CI configuration so that when a CI job is re-run for a pull request, it checks out the latest merged state of that PR branch rather than a possibly stale cached version. The change is purely in the CI workflow file and does not touch Bitcoin Core's actual code, consensus logic, wallet, or networking. It is a reliability/correctness improvement for automated testing, not a fix for a vulnerability in the Bitcoin software itself.

This commit updates the libmultiprocess subtree used by Bitcoin Core. The most notable change is a build-time check that refuses to compile with older, vulnerable versions of the Cap'n Proto library (CVE-2022-46149) and with Cap'n Proto versions that are incompatible with Clang 16+ under C++20. It also adds FreeBSD and macOS CI jobs, fixes example build instructions, and reduces the maximum size of IPC debug log messages from 1000 to 200 characters via a new LogOptions struct.

This commit is a straightforward code-quality change: it adds the word 'const' to a notification callback parameter so subscribers receive a read-only view of the current block tip index. It does not fix a bug, close a vulnerability, or change any behavior. It simply prevents future implementations of the callback from accidentally modifying the index.

This commit only changes Bitcoin Core's continuous integration (CI) test scripts. It adds the Python pycapnp package to several CI environments so that inter-process communication (IPC) tests run on more platforms. There is no change to the Bitcoin software that users run, and no security vulnerability is present in the diff.

This commit only changes Bitcoin Core's continuous integration (CI) test setup. It installs the Python pycapnp package so that inter-process communication (IPC) tests can run automatically in GitHub Actions. There is no change to the actual Bitcoin node code that users run, and nothing in the commit suggests a security vulnerability or fix.

This commit only adds new automated tests for Bitcoin Core's IPC (inter-process communication) interface. It does not change any production code, wallet logic, consensus rules, or network behavior. There is no security issue here.

This commit only adds test infrastructure so that Bitcoin Core's functional test suite can detect whether the software was built with IPC (inter-process communication) support and skip tests that require it. It does not change any production code, network behavior, or wallet logic, and it introduces no security issue.

This commit is a harmless test-infrastructure change. It tells the Bitcoin Core test framework where to find the new `bitcoin` wrapper binary by adding an environment variable override (`BITCOIN_BIN`) and a default path. There is no security issue here.

This commit only changes the Bitcoin Core test framework. It adds a convenience option so automated tests can more easily start a test node with inter-process communication (IPC) enabled. It does not change the production Bitcoin Core software that users run, and there is no indication it fixes or introduces a security problem.

This change is a user-experience and reliability fix, not a security patch in the traditional sense. It stops Bitcoin Core from starting when the user accidentally gives it the same network binding address twice (for example, '-bind=0.0.0.0 -bind=0.0.0.0'). Previously the node would crash later with a confusing 'already running' message. Now it exits early with a clear message about the duplicate configuration. There is no evidence it fixes an exploitable vulnerability.

This commit only changes build tooling configuration. It tells the clang-tidy static analyzer to ignore a specific warning class in generated IPC source files because the upstream Cap'n Proto project considers the warnings false positives. There is no change to Bitcoin Core's runtime code, no bug fix, and no security-relevant behavior change.

This commit simply changes two log messages from 'warning' level to 'debug' level in the network code that handles NAT-PMP/PCP router discovery. When a router does not support these protocols, the software was printing warnings that could flood logs; now those messages only appear in debug logging. There is no security vulnerability being fixed here.

This commit is not a focused code patch. The supplied diff shows the addition of thousands of unrelated repository files (CI configs, templates, build files, documentation, source trees, etc.) under a commit title that only mentions a GCC/systemtap tracing workaround. The actual claimed change is not visible in the provided diff, so there is no basis to assess any security issue.

This commit only changes the sizes of virtual machines used by Bitcoin Core's automated testing pipeline on GitHub. It switches several jobs from medium/large runners to smaller ones to save computing resources. There is no change to the Bitcoin software itself, no user-facing change, and no security relevance.

This commit simply adds a documentation file: the archived release notes for Bitcoin Core version 29.1. It contains no code changes, no configuration changes, and no executable modifications. It is purely informational text describing what was already released in version 29.1.

This commit only changes a single comment in a build script. It updates the explanation for why a library path is set on macOS, because the previous comment mentioned only Qt but the build now also uses another native package (capnp). No code behavior changes.

This is a small internal cleanup in Bitcoin Core's coin statistics index. It removes repeated calls checking whether a transaction is a coinbase transaction by storing the result once in a local variable, and marks a few objects as const so the compiler can enforce they are not modified. There is no change to network rules, consensus logic, or user-facing behavior.

This commit simply renames a private internal function from 'ReverseBlock' to 'RevertBlock' because the new name better describes what the function does during blockchain reorganizations. No behavior, logic, or security properties change.

This commit changes the Bitcoin Core build system so that when Qt (the graphical user-interface library) is installed into the dependency staging area, its binaries are stripped of debug symbols. The change only affects build artifact size and does not alter runtime behavior, network protocol, wallet logic, or consensus code. It is a build-size optimization, not a security fix.

This commit is a routine cleanup of Bitcoin Core's continuous integration (CI) scripts. It removes an unused environment variable called RUN_UNIT_TESTS_SEQUENTIAL and merges its behavior into the standard unit test path. There is no change to the Bitcoin software that users run, no security fix, and no vulnerability.

This commit fixes how Bitcoin Core reads network routing information from the Linux kernel. Previously, the code only made one request and could receive incomplete routing data on systems with large routing tables, or could hang waiting for a 'done' signal that never comes. The fix loops to collect all kernel response parts and only waits for the 'done' marker when the kernel says the response is multi-part. This is a reliability bug fix, not a direct money-stealing vulnerability, but incorrect routing data could affect how the node connects to peers.

This commit adds a small in-memory cache to Bitcoin Core's wallet so it can remember whether a transaction spends coins that belong to the wallet, instead of recalculating that fact every time it is needed. It is a performance and code-clarity change, not a fix for a known security bug. There is no evidence in the commit or supplied references that this addresses an active vulnerability.

This commit only adds a new automated test for Bitcoin Core's wallet behavior regarding 'anchor outputs'—a special zero-value or tiny output type used in some transaction protocols. It does not change any production wallet, node, or consensus code. The test verifies that the wallet can detect anchor outputs during a blockchain rescan but cannot spend them. There is no security vulnerability here.

This commit changes the Bitcoin Core wallet's 'sendall' RPC command so that instead of relying on an internal assumption that every coin's size is known, it explicitly checks whether the final transaction size can be calculated and throws a clear error if it cannot. Previously, the code used a non-fatal assertion that could be skipped in release builds, potentially allowing the command to proceed with an invalid or unknown transaction size when the wallet contained descriptors it could not fully solve.