rust-bitcoin

This commit is a purely cosmetic code-formatting change. It reorders three import statements in a single Rust source file so they appear alphabetically, with no functional effect on the program.

This commit is purely cosmetic: it reorders two crate re-exports (base58 and base64) in a source file to satisfy the project's code formatter. There is no functional change, no bug fix, and no security relevance.

This commit only updates an internal Rust test file to include additional module names in a list of crate-root modules. It does not change any actual library code, behavior, or security-sensitive logic. There is no apparent security relevance.

This commit only adds new test cases to a public API surface test file. It imports recently-added encoder/decoder types from several modules to ensure they are reachable by users of the library. There is no code change to the library itself, no bug fix, and no security-related content.

This commit adds a new test file that checks the public API surface of the consensus_encoding crate. It only imports types, checks that they implement common traits like Debug, Clone, Default, Send, and Sync, and verifies that Debug output is non-empty. There is no change to production code or security-sensitive logic.

This commit only updates generated API listing files (text snapshots of public functions) to include a newly added public function. It does not change any actual source code, behavior, or fix any problem. There is no security relevance.

This commit only adds a new automated test for an existing function called hash_64_many. It does not change any production code, fix a bug, or alter behavior. There is no security issue here.

This commit simply moves an existing SHA256 midstate-to-engine conversion from one place in the code to another. The actual logic is unchanged; it is a code-organization refactor following a Rust API design guideline. There is no security fix or vulnerability here.

This commit only updates generated API snapshot text files to include a newly added public function, `Midstate::to_engine`. It does not change any source code, fix a bug, or alter program behavior. There is no security relevance visible in the commit itself.

This commit is purely a code formatting cleanup. It removes blank lines, reorders some import/module declarations, and collapses a few trivial function bodies onto one line. There are no functional changes to how the software behaves, and no security implications.

This commit only updates generated API snapshot files that list what types and functions are publicly available in the library. It adds entries for a new Signet-related script type that was already introduced elsewhere in the codebase. There is no actual code change, no bug fix, and no security relevance visible in the diff.

This commit is a straightforward code-quality improvement in the rust-bitcoin library. It introduces new type names (SignetBlockScript and SignetBlockScriptBuf) to represent signet challenge scripts more clearly, replacing the previous use of WitnessScript types. There is no security bug being fixed here and no behavior change that would affect users' funds or network safety.

This commit only updates generated API text files that list the public interface of the Rust Bitcoin crates. The changes reflect newly added standard Rust trait implementations (From<Infallible>) for various error types. These are not code changes and do not alter runtime behavior, so there is no security impact.

This commit adds standard Rust trait implementations that let the library's error types be automatically converted from an 'impossible' error type (Infallible). It is a routine API-ergonomics improvement with no security relevance: Infallible can never actually be produced at runtime, so these conversions can never be triggered by an attacker.

This commit is a routine API refactor in the rust-bitcoin library. It changes the message-signing function so it accepts a higher-level PrivateKey reference instead of a low-level secp256k1 secret key, and moves the underlying signing logic into a new PrivateKey method. There is no indication this fixes a security bug; it is a design cleanup to hide internal cryptographic types from users and prepare for future API changes.

This commit is purely a code-formatting cleanup. It removes blank lines, collapses a struct literal onto one line, reorders re-exports and module declarations, and adds a blank line between imports. There is no functional change and no security relevance.

This commit only adds a code-formatting check to the project's continuous integration (CI) pipeline and updates the contributor guide to explain the formatting policy. It does not change any production code, cryptographic logic, network handling, or data parsing. There is no security issue here.

This commit only rearranges code comments in a test file to prevent an automated code formatter from reformatting them awkwardly. No program logic, behavior, or security-sensitive code was changed.

This commit only runs an automated code formatter. It reorders imports, removes blank lines, and collapses some struct literals onto single lines. There are no functional code changes and no security relevance.

This commit is a routine maintenance update to the project's automated testing setup. It upgrades an internal tool called cargo-rbmt and moves its configuration from separate files into each crate's Cargo.toml package metadata. It also changes how nightly and stable Rust compiler versions are tracked, storing them in the workspace Cargo.toml instead of separate version files. There are no changes to the actual Bitcoin library code that users depend on, and no security-relevant behavior is modified.

This commit only removes documentation comments from public crate re-exports. It does not change any executable code, APIs, or behavior. There is no security relevance.

This commit only updates generated API snapshot text files. It removes lines that list certain error-conversion functions from the public API surface, but it does not change any actual Rust source code, logic, or behavior. There is no security-relevant change visible in the diff.

This commit removes automatic conversion traits (From implementations) that let sub-errors be silently turned into parent errors. It replaces them with explicit error wrapping at each call site. This is a code-quality and API-clarity change, not a security fix. There is no evidence in the commit message or diff that it addresses a vulnerability, exploit, or bug that could affect users.

This commit is purely a code-formatting cleanup. It removes blank lines, reorders imports, and lets an automated formatter rewrap a few lines. There are no functional changes to how the software behaves, and nothing in the diff suggests a security fix or vulnerability.

This commit fixes a small but real bug in a Bitcoin peer-to-peer networking library written in Rust. A helper object that encodes message command names (like "version") was incorrectly reporting that it always had 12 bytes left to send, even after some bytes had already been consumed. The fix makes it report the actual remaining length. The bug could mislead callers that rely on the remaining-length promise, but the commit does not show a direct path to stealing funds or remote code execution.