Bitcoin Core

This commit loosens an internal build-time check that verifies which compiler/library versions Bitcoin Core's release binaries are allowed to depend on. It does not change the actual code users run, fix a crash in normal operation, or patch a vulnerability. The change was needed because a recent code update (#32750) legitimately uses a compiler helper symbol that only exists in GCC 7+, so the release-build script had to be updated to permit that symbol. No security bug is being fixed.

This commit only updates documentation text to reflect a previously changed default fee rate. It does not modify any code, network behavior, or security logic, so it has no direct security impact.

This commit only adds a release note document explaining upcoming changes to default Bitcoin transaction fee rates. It contains no code changes and no security fix or vulnerability.

This commit lowers Bitcoin Core's default minimum relay fee and replacement fee from 1000 satoshis per kilovbyte to 100 satoshis per kilovbyte. The stated goal is to make it cheaper for legitimate transactions to propagate while still keeping spam-based bandwidth attacks more expensive than renting commercial bandwidth. It is a deliberate policy change, not a code vulnerability, but it changes the economics of transaction relay and mempool replacement across the network.

This is a small test-only change in Bitcoin Core. It adjusts a mock mempool helper used in automated tests so that fee calculations line up more precisely when non-integer fee rates are used. The change only affects test code and does not alter how the live Bitcoin network or wallet behaves.

This change lowers the default minimum fee a Bitcoin miner requires to include a transaction in a block from 1000 satoshis per kilovbyte to 1 satoshi per kilovbyte. The intent is to let miners include any transaction already accepted by their mempool, rather than having a separate, stricter block-inclusion rule. It is a policy/configuration change, not a cryptographic or consensus bug, and it does not bypass mempool rules.

This commit only changes test code. It replaces hard-coded fee rate numbers like 1000 with named constants and removes duplicated hard-coded values in test assertions. There is no change to the actual Bitcoin Core node behavior, so it cannot introduce a security vulnerability or fix one in production code.

This commit only changes a single functional test file. It explicitly sets the minimum relay transaction fee in the test setup so the test's assumptions about fees are clear. There is no change to production wallet, consensus, or networking code, and no security issue is present.

This commit adds a compile-time check (static_assert) to ensure two internal fee constants are equal. It is a documentation/safety assertion with no functional code change and no security impact on its own.

This commit only adds new test code that checks the default values of two Bitcoin network fee settings. It does not change any production code, wallet behavior, or network rules. There is no security issue here.

This commit only adds new automated tests for Bitcoin Core's Replace-By-Fee (RBF) fee-bumping rules. It does not change any production code, network protocol, or wallet behavior. The tests verify that a transaction replacement must pay a higher fee when the node's '-incrementalrelayfee' setting is raised. There is no security fix or vulnerability patch here.

This commit only adds a new automated test to Bitcoin Core. It checks that a special new transaction type (TRUC, also known as version 3 transactions) can enter the mempool as a package even when one part pays no fee, while ordinary transactions cannot bypass the minimum relay fee. The change does not modify any production code, so it cannot directly affect live Bitcoin nodes or funds.

This commit only adds a new test to Bitcoin Core's test suite. It checks that when miners set a minimum transaction fee above zero, the block template does not include completely free (zero-fee) transactions. There is no change to production code, no bug fix, and no security patch.

This commit is a pure code reorganization: it moves a header file that defines transaction ID types (Txid, Wtxid) from one directory to another and updates all the places that include it. There are no functional changes to how Bitcoin Core behaves, and no security issue is present.

This commit removes shortcuts that let a new transaction ID type be silently treated as the older uint256 type. It is a code-cleanup change that makes type mismatches produce compile-time errors rather than compile silently. There is no direct evidence this fixes an exploitable vulnerability; it is a hardening/refactoring step.

This is a code cleanup change that replaces generic 256-bit hash values with more specific transaction ID types (Txid and Wtxid) across many files. It does not change what the program computes or how it protects data; it only makes the type names more precise so developers can catch category mistakes at compile time. There is no indication this fixes a security bug.

This commit is a straightforward code cleanup that swaps the generic uint256 type for the more specific Txid type in transaction-related policy code. It does not change behavior, fix a bug, or introduce a security vulnerability. It is purely a type-safety refactor.

This commit is a straightforward internal code cleanup in Bitcoin Core. It replaces the generic 256-bit hash type (uint256) with more specific transaction ID types (Txid and Wtxid) in the memory pool and related code. There is no change to network rules, consensus logic, or user-visible behavior, and no security vulnerability is introduced or fixed.

This is a straightforward internal code cleanup: Bitcoin Core's mini-miner and mempool code are switching from a generic 256-bit hash type (uint256) to a more specific transaction-id type (Txid). No behavior changes, no bug fixes, and no security relevance are visible in the diff.

This commit is a code cleanup that replaces the generic uint256 type with a more specific Txid type when handling transaction identifiers in RPC commands and merkle block processing. It does not change program behavior, fix a bug, or introduce a security feature. It is a type-safety refactor intended to make the code clearer and harder to misuse in the future.

This commit simply bumps the version of a third-party GitHub Action used to check out source code during automated testing, from v4 to v5. There is no indication of a security vulnerability being fixed or introduced. It is a routine maintenance update to the project's continuous integration configuration.

This commit fixes a test-only bug in Bitcoin Core's unit tests. The test was accidentally creating empty or wrong-sized data blobs because the arguments to a vector constructor were swapped. This only affects test code, not the live Bitcoin network or wallet software, so it has no security impact on real users.

This commit only adds user-facing log messages that announce when Bitcoin Core turns signature checking on or off during initial block download. It does not change whether signatures are checked, only how clearly the node tells the user about it. There is no security vulnerability here.

This is a small cleanup change to Bitcoin Core's internal logging code. It fixes a minor bug where a '[*]' indicator that warns operators some log messages are being suppressed was only shown in one specific case, and now shows it whenever any suppression is active. It also removes a few redundant newline characters and adjusts a log message severity from 'Info' to 'Warning'. There is no direct security vulnerability here; it is a reliability/usability improvement for log output.

This commit is a straightforward internal code cleanup in Bitcoin Core's logging system. It renames a helper class and moves it inside another class, with no change to how log rate-limiting behaves. There is no security issue here.