rust-bitcoin

This commit is a code-style refactor. It replaces single-line Rust conditional annotations like #[cfg(all(A, B))] with stacked separate lines like #[cfg(A)] #[cfg(B)]. The behavior is identical; no security issue is introduced or fixed.

This commit only fixes the wording and formatting of documentation comments in four source files. It adds backticks around hash function names like `SHA256d` and `SipHash24` so the generated documentation looks consistent. No code behavior changes.

This commit is a routine internal refactoring of the rust-bitcoin project. It moves a helper macro called transparent_newtype from one internal crate to a shared include file, then updates all crates to use the shared version. There is no change to user-facing behavior, no bug fix, and no security relevance.

This commit is purely a housekeeping change to the project's continuous integration (CI) setup. It moves the files that record the library's public API surface from a shared top-level directory into each individual crate's own directory, and switches the CI workflow to use a different command to check those API files. There is no change to the actual Bitcoin library code that users run, and no security impact.

This commit is purely a code formatting cleanup. It only reorders an import statement, removes extra blank lines, and reformats an array literal to fit style guidelines. There are no functional changes to the SHA-256 hashing code.

This commit only adds `#[rustfmt::skip]` annotations to three places in a SHA-256 cryptographic implementation file. These annotations tell Rust's automatic code formatter to leave those blocks alone. There is no change to program logic, constants, memory handling, or any behavior that could affect security.

This commit is a pure code reorganization: it moves existing error type definitions from several source files into a new dedicated `error` submodule and re-exports them at the crate root. There are no functional changes to how data is encoded or decoded, no bug fixes, and no security-relevant behavior changes.

This commit adds a single blank line in source code between a type declaration and a function declaration for formatting consistency. It does not change any behavior, logic, or security properties of the software.

This commit only reformats documentation comments (rustdoc) in five source files to match the project's preferred 100-column line width. No executable code, logic, or behavior was changed. It is a cosmetic/style-only change with no security relevance.

This commit only fixes grammar in code comments (changing 'Push' to 'Pushes' and 'Complete' to 'Completes'). It does not change any actual program logic, function behavior, or security properties.

This commit simply updates a pinned nightly Rust compiler version in a project file from one weekly snapshot to the next. It is a routine tooling/maintenance change with no visible security relevance.

This commit is a routine API cleanup in the rust-bitcoin library. It adds new helper methods so that developers can create cryptographic keypairs directly from PrivateKey objects instead of reaching into the underlying secp256k1 secret key. The change does not fix a bug, close a security hole, or alter cryptographic behavior; it only makes the public API more convenient and less error-prone.

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 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 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 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 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 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 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 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.