Bitcoin Core

This commit removes a temporary workaround that was only needed for a bug in older Microsoft Visual Studio compilers. The workaround wrapped certain fixed Bitcoin block hashes so the compiler would accept them. Now that the compiler bug is fixed, the code can use the hashes directly. There is no change to Bitcoin's rules, data, or security.

This commit is a routine build-system maintenance change. It updates Bitcoin Core's Windows build instructions and automated CI scripts to require a newer version of Microsoft Visual Studio (VS 2026 instead of VS 2022). There is no change to the actual Bitcoin node code, wallet logic, networking, or consensus rules, and nothing in the commit suggests a security fix or vulnerability.

This change adjusts how Bitcoin Core builds an internal cryptographic library (libsecp256k1) so that its internal function names are no longer exposed in the final library files. It is a hardening/cleanup change rather than a fix for an active bug or exploit. The commit message frames it as preventing implementation-detail symbols from leaking out of the kernel library, which can reduce attack surface but does not by itself fix a known vulnerability.

This commit is a simple code cleanup: it renames a local variable from 'descendant_count' to 'unused_cluster_count' in two wallet files to make clear that the value is not actually used. There is no functional change, no bug fix, and no security relevance.

This is a minor cleanup change in a test script only. It rewords a comment, removes a one-second sleep, and extends the effective timeout from 60 to 120 seconds (the loop already used 120, but the docstring said 60). It does not touch production code, network behavior, or wallet handling, so it has no security relevance for Bitcoin users.

This is a minor change to Bitcoin Core's continuous integration (CI) script. It adjusts how many lines of surrounding context are shown when checking code formatting. There is no security issue here.

This commit adds the recipient's network address to the bookkeeping records used by Bitcoin Core's private transaction broadcast feature. It does not change how transactions are sent or validated; it only stores extra metadata for internal tracking. There is no direct security vulnerability visible in the change, and the commit message does not describe it as a security fix.

This commit is a minor code cleanup in a Windows CI (continuous integration) helper script. It replaces older-style file path construction with a newer Python standard library approach. There is no security-relevant change and no user-facing behavior change.

This change simply moves existing Windows unit-test commands out of a GitHub workflow file and into a Python helper script. It is a pure code reorganization with no visible security relevance.

This is a small change to Bitcoin Core's internal continuous integration (CI) scripts. It moves the location where downloaded previous Bitcoin releases are stored from a temporary CI folder to the current workspace directory, making it easier for developers to reproduce CI test runs on their own machines. There is no user-facing change, no wallet or network code change, and no security issue visible in the diff.

This commit is a straightforward internal cleanup of Bitcoin Core's Windows CI (continuous integration) script. It moves the existing functional-test command from the GitHub Actions YAML file into a Python helper script, with no changes to the actual Bitcoin node code that users run. There is no security-relevant change visible in the diff.

This commit is a pure internal cleanup of Bitcoin Core's continuous integration (CI) scripts for Windows builds. It moves two steps—downloading previous Bitcoin releases and installing a Python library called pyzmq—into a single Python helper script. There is no change to the Bitcoin software that users run, no change to wallets, networking, consensus rules, or cryptography, and no security-relevant behavior is introduced.

This commit is a straightforward internal cleanup of Bitcoin Core's Windows CI workflow. It moves the rewriting of test/config.ini from a PowerShell inline step in the GitHub Actions YAML file into a Python helper script. There is no change to what gets written, no user-facing behavior change, and no security relevance.

This is a test-only change in Bitcoin Core's miniscript unit tests. It swaps one internal test assertion (checking script size) for another (checking tree depth) so that the test can reliably detect stack-unsafe destructor implementations under CI's reduced stack size. It does not change production code, consensus rules, network behavior, or wallet operations.

This change simply moves an existing Windows CI check from a GitHub Actions workflow file into a Python helper script. It does not change what the check does, only where the code lives and which folder temporarily holds one output file. There is no security issue here.

This commit is a routine cleanup of the project's automated Windows build testing. It moves a single step—printing the version of the compiled Bitcoin daemon—out of the GitHub Actions workflow file and into a small Python helper script. There is no change to the Bitcoin software users run, no security fix, and no vulnerability introduced.

This change makes Bitcoin Core's transaction-graph cluster linearization use a deterministic fallback ordering when the optimal algorithm ties or cannot fully decide. Previously the fallback relied on internal index numbers, which could leak information about how transactions are stored internally. The new fallback uses actual transaction properties (feerate, weight, txid) and an externally supplied order, making behavior predictable and less dependent on internal memory layout. It is a hardening/feature improvement rather than a fix for an active exploit.

This commit removes random tie-breaking when Bitcoin Core's transaction-cluster linearization algorithm orders equal-feerate transactions or chunks. It replaces the random choice with a deterministic fallback comparator. The change is described by the author as a feature, not a security fix, and the commit message explicitly notes that txgraph's overall ordering is still not fully deterministic because internal indexes can still be assigned randomly. Tests are updated to expect exact orderings instead of just comparing fee-rate diagrams.

This commit changes how Bitcoin Core's new transaction graph (TxGraph) orders groups of transactions (called 'chunks') when they have the same transaction fee rate but come from separate, unrelated clusters of transactions. It introduces a tie-breaker based on the total size of consecutive same-fee-rate chunks within a cluster. The change is described by the project as a feature improvement, not a security fix, and includes new fuzz-test checks to verify the ordering behaves consistently.

This is a small internal preparation change in Bitcoin Core's new transaction-graph code. It makes the index-compaction routine notify affected transaction clusters after graph indexes are swapped, so that future code can safely store extra index-based data. The commit itself does not introduce or fix any currently reachable bug; it only lays groundwork and adds defensive consistency checks.

This is a small internal cleanup in Bitcoin Core's new transaction graph code. It makes sure that when a transaction reference object is destroyed, any cached 'chunk index' bookkeeping for its cluster is wiped out. The commit message explicitly says this is preparation for a future feature and is not currently a problem, because the index is not observable by outside code until the cluster is reprocessed anyway. There is no direct evidence this fixes an exploitable security bug.

This commit changes how Bitcoin Core orders transactions inside a 'chunk' during a process called cluster linearization. Previously, transactions within a chunk were picked in a random order; now they are sorted by fee rate (highest first) and then by size (smallest first), while still respecting parent-before-child dependencies. This is a deliberate feature change, not a security fix, and includes new fuzz tests to verify the ordering rules.

This commit changes how Bitcoin Core orders groups of related transactions (called 'chunks') in its internal transaction graph. It replaces a non-deterministic tie-breaker based on internal cluster sequence numbers with a deterministic one based on transaction IDs. The goal is to make the mempool ordering fully predictable, which helps with testing and may reduce subtle consensus or network behavior differences between nodes. There is no indication this fixes an active security vulnerability.

This commit only changes an internal fuzz test file. It replaces direct use of a base class (TxGraph::Ref) with a new empty subclass (SimTxObject) inside the test code, so the test structure better matches how the real mempool uses derived objects. There is no change to production code, network behavior, wallets, consensus, or any user-facing functionality.

This commit is a pure internal refactoring in Bitcoin Core. It adds a new optional tie-breaker function (called fallback_order) to the transaction graph (TxGraph) code, but explicitly does not use it yet. It is preparation for future work and does not change any network behavior, consensus rules, or security properties.