Bitcoin Core

This commit adds a new read-only field called 'script_flags' to the getdeploymentinfo RPC response. It simply reports which Bitcoin script verification rules are active for a given block. There is no code change that modifies how transactions or blocks are validated, accepted, or relayed. It is an informational API enhancement with no apparent security impact.

This commit widens an internal Bitcoin Core data type used for script verification flags from 32 bits to 64 bits. It is a forward-looking capacity increase so more verification options can be added in the future. There is no indication it fixes an active security bug.

This commit is a straightforward internal code cleanup in Bitcoin Core. It changes how script verification flags are defined from being bit-shifted numbers directly in the enum to plain sequential numbers, with the bit shifting done later when converting to the actual flags type. There is no security vulnerability or behavior change intended here.

This commit is a pure code cleanup: it creates a single type name, script_verify_flags, and uses it everywhere script verification flags were previously written as uint32_t, unsigned int, or unsigned. The actual data type is still uint32_t, so behavior is unchanged. There is no security fix or vulnerability here.

This commit is a code-quality refactor, not a security fix. It replaces a plain 32-bit integer type used for Bitcoin script verification flags with a dedicated C++ class that prevents accidental mixing with regular integers. The change makes the code safer to maintain but does not alter what the flags mean or how transactions are validated.

This commit simply makes an internal helper function visible to other parts of the codebase. It does not change what the function does, what data it can access, or how Bitcoin validates blocks. There is no security issue here.

This commit is a straightforward code cleanup: it moves a helper that converts script verification flags into human-readable names from test files into a shared library location, and adds a small test for it. There is no change to how Bitcoin validates transactions or scripts, and no security fix.

This is a small code cleanup (refactor) that removes always-true return values from two database helper functions. The return values were never checked by callers, so the change has no effect on behavior and no security relevance.

This commit is a simple code cleanup (refactor) in Bitcoin Core. Three functions previously returned a boolean value that was always 'true' and was always ignored by callers. The change removes those always-true return values and updates the callers accordingly. There is no security-relevant change: no new behavior, no bug fix, no vulnerability introduced or fixed.

This is a code cleanup change. A helper function that always returned 'true' is changed to return nothing, and callers are updated to stop checking a result that could never fail. There is no security-relevant behavior change.

This is a small internal code cleanup in Bitcoin Core's optional transaction index. The WriteTxs helper always returned true, so the caller now skips checking it and directly returns true. There is no user-facing or security-relevant change.

This is a straightforward code cleanup change. A database helper function that always returned true is changed to return nothing, and callers are updated to stop checking a value that could never be false. No security bug is introduced or fixed.

This is a trivial comment and constant update in a tracing demonstration script. It changes a documented maximum string length from 118 to 114 characters because a previous commit shortened the longest possible rejection reason. There is no security issue.

This commit is a simple automated rename of user-facing error messages and test expectations. It changes the phrase 'mandatory-script-verify-flag-failed' to 'block-script-verify-flag-failed' across source code and tests. No validation logic, security checks, or behavior changes.

This commit adds a new read-only diagnostic field called 'inv_to_send' to the getpeerinfo RPC output. It simply reports how many transaction announcements are queued for each peer. There is no change to network behavior, transaction relay logic, or access controls.

This is a routine internal code cleanup in Bitcoin Core. It removes a redundant method called getActiveChainLocator and replaces its uses with an existing equivalent method, findBlock. There is no security fix here and no indication this change addresses any vulnerability.

This commit is a routine code cleanup. It removes an unused function called getTipLocator and a related internal helper, replacing one remaining use with an equivalent existing function. There is no security-relevant change.

This is a test-only code change that fixes a flaky unit test. The test previously borrowed a real block index object from the main chain and modified it, which could race with other test threads. The patch creates a local copy of the index data instead, so the test no longer touches shared state. It is not a fix for a security vulnerability in Bitcoin Core itself.

This commit is a routine localization fix for Bitcoin Core's wallet. It makes the words '[default wallet]' in progress messages translatable, so non-English users see a fully translated message. There is no security impact.

This commit only updates user-facing build instructions in documentation files. It changes wording to say SQLite is required for wallet builds (rather than only for 'descriptor wallets') and tells users how to disable the wallet if they don't want it. There are no code changes, no bug fixes, and no security-relevant behavior changes.

This commit adds a hidden debug-only command-line option that lets users turn off a recently-introduced log rate limiter. By default the rate limiter stays on, so normal users are not affected. The change is mainly useful for developers running tests who need full logs. It does not by itself create a new security hole, but it does expose a switch that could theoretically be used to disable a protection against disk-filling attacks.

This commit is a simple code cleanup in Bitcoin Core's test suite. It creates a small helper function that reads log files during testing, replacing four nearly identical blocks of test code. There is no change to the actual Bitcoin node software, no change in behavior, and no security relevance.

This commit only changes test code in Bitcoin Core. It refactors and improves the clarity of existing unit tests for the logging rate limiter. There are no changes to production code, so it cannot directly affect live Bitcoin node behavior or introduce a security vulnerability.

This is a test-only cleanup. It makes sure that one logging test does not accidentally leave its settings behind and affect later tests. There is no change to the actual Bitcoin Core software that users run, and no security issue in production code.

This commit changes how Bitcoin Core's log rate-limiter is managed in memory. Previously, the scheduler held a raw pointer to the limiter, which could become invalid if the limiter was destroyed while a scheduled reset task was still pending. The fix makes the limiter a shared pointer and gives the scheduler only a weak reference, so the scheduled task safely does nothing if the limiter is gone. This is a defensive hardening change, not an active exploit fix.