rust-bitcoin

This commit adds automatic memory clearing when Bitcoin private key objects are destroyed. It is a defensive hardening change, not a fix for an active vulnerability. The change reduces the chance that secret key material lingers in memory after use, but the commit itself does not claim to fix any known exploit.

This commit removes the automatic byte-by-byte copying trait (Copy) from the PrivateKey type in the rust-bitcoin library. The goal is defensive: secret key material is less likely to be silently duplicated in memory, which can reduce the number of places an attacker or memory-dump tool might find leftover private key bytes. It is a hardening change, not a fix for an active exploit or a specific bug.

This commit removes the automatic 'Copy' trait from two Bitcoin key types that hold secret data (Keypair and TweakedKeypair). In Rust, 'Copy' makes it easy for the compiler to silently duplicate values, which can increase the chances of secret key material being copied around in memory unexpectedly. The change also renames a method from 'to_keypair' to 'into_keypair' and adjusts related code. It is a defensive hardening measure, not a fix for a known active exploit.

This commit only adds Rust compiler hints (`#[inline]`) to a few small functions that convert Bitcoin merkle node values to and from bytes. It does not change what the code does, only gives the compiler a stronger suggestion to embed these tiny functions at call sites. There is no security relevance.

This commit simply rearranges the order of code blocks in two files. It moves the implementations of the Encodable and Decodable traits so they appear before the helper encoder/decoder struct definitions, matching a previous cleanup done for BlockHash. No logic, behavior, or security properties are changed.

This commit changes a single Rust function from a regular function to a constant-evaluable function. It allows the decoder constructor to be used in compile-time contexts, but it does not fix any security bug or change runtime behavior.

This commit is a routine code cleanup in the rust-bitcoin library. It changes how certain traits from another crate are imported and referenced, adding an 'encoding::' prefix and using 'as _' for traits that are only needed for their methods. There is no functional change to how the software behaves, and no security issue is present.

This commit only runs an automatic code formatter (rustfmt) across three source files. It changes whitespace, line breaks, and indentation but does not alter any program logic, function behavior, or security properties. There is no security issue here.

This commit only updates a generated text file that lists the public API surface of the crate. It records that three error types now automatically implement Clone and equality comparison traits. No actual source code behavior changed, and nothing in the commit suggests a security fix or vulnerability.

This commit is a routine code cleanup. It removes hand-written Debug formatting code for three error types and instead lets Rust automatically generate Debug, Clone, PartialEq, and Eq behavior. There is no security-relevant change here.

This commit adds standard Rust trait implementations (Clone, PartialEq, Eq, and Debug) to a custom error type called ParsePrimitiveError. It is a routine code-quality improvement that lets other error types automatically derive these same traits when they wrap ParsePrimitiveError. There is no security fix or behavior change here.

This commit only runs an automated code formatter (rustfmt) across three files. It changes whitespace, line breaks, and indentation but does not alter any program logic, function behavior, or security-relevant code paths.

This commit only changes a test file. It removes some test assertions that compared the library's PSBT output against fixed BIP-174 test vectors, because the project is switching to a different default signature style (low_r) that produces different but still valid signatures. No production code is changed, and no security vulnerability is introduced or fixed.

This commit adds a convenience method so that a Bitcoin private key object can directly create an ECDSA signature, instead of forcing callers to reach into the underlying secp256k1 library. It also updates internal code and an example to use the new method. There is no obvious security bug in the change itself, but it slightly changes how nonces are generated for signatures: the new helper uses a 'low-R' nonce-grinding scheme, whereas the previous PSBT code used the default signing path. That is generally a compatibility improvement, not a vulnerability, but it is a behavior change worth noting.

This commit only runs an automatic code formatter (rustfmt) across three source files. It changes whitespace, line breaks, and indentation but does not alter any program logic, function behavior, or security properties. There is no security issue here.

This commit only adds new test code. It checks that error messages display correctly and that error sources are linked properly for transaction-related decoding failures. No production code behavior was changed, so it does not introduce or fix a security vulnerability on its own.

This commit only adds new automated tests to the transaction module. It does not change any production code, fix bugs, or alter behavior. There is no security issue here.

This commit only adds new automated tests that check how many bytes various transaction decoders expect to read next. It does not change any production code, fix a bug, or alter behavior. There is no security issue here.

This commit is a minor test-code cleanup. It replaces a verbose match statement with Rust's built-in matches! macro to check that an error is the expected type. There is no change to production code, no security fix, and no vulnerability.

This commit is a simple cleanup of internal unit tests. It replaces repeated hard-coded byte lists with named constants inside test code. There is no change to the actual library behavior, no bug fix, and no security relevance.

This commit is purely a code-style change. It reverts an automated formatting bot's changes to two test macros and adds markers telling rustfmt to leave them alone in the future. There is no functional change to the program and no security relevance.

This commit corrects a single spelling mistake in the package description within a configuration file. It changes 'eccosystem' to 'ecosystem' and has no effect on program behavior, security, or functionality.

This commit only updates documentation comments in three Rust source files to add clickable cross-references (rustdoc links). No executable code, logic, or behavior was changed. It cannot affect security.

This commit only updates generated API snapshot files (text files listing public types, functions, and module paths). It reflects a code reorganization where several error types were moved into new `error` submodules, but the commit itself does not change any source code or behavior. There is no security fix or vulnerability here.

This commit is a straightforward internal code reorganization. It moves an error type related to decoding transaction sequence numbers into a new 'error' submodule and re-exports it. There is no functional change to how the library behaves, and no security issue is present.