rust-bitcoin

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 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 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 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 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 purely a code-formatting change. It rewraps a long `#[deprecated(...)]` attribute in a Rust source file onto multiple lines so it complies with the project's style rules. No logic, behavior, or security properties of the code were changed.

This is a tiny internal code cleanup that changes how a compressed Bitcoin public key is printed as text. It swaps one standard way of turning bytes into hex for another equivalent way. There is no security issue here.

This commit adds convenience conversion methods so that a CompressedPublicKey can be created directly from a secp256k1 public key or a keypair, matching the existing abilities of the regular PublicKey type. It is a routine API usability improvement with no apparent security relevance.

This commit adds a new convenience method called force_compressed to the PublicKey type in the rust-bitcoin library. It lets callers convert a public key into a compressed public key without handling a possible failure case. The change is purely additive (8 new lines, no deletions) and does not alter existing behavior or fix any bug. There is no indication of a security issue in the commit or supplied references.

This is a routine API cleanup, not a security fix. The developers renamed a function from from_slice to from_bytes on CompressedPublicKey so the name better matches that it now accepts a fixed 33-byte array. The old from_slice is kept but marked deprecated, and internally it now checks the slice length before delegating. No vulnerability is described or fixed.

This commit is a routine API cleanup: it stops publicly re-exporting a few specialized hash types (Ntxid, TxMerkleNode, WitnessMerkleNode) from convenient crate-root locations, so users must import them from their original modules instead. It does not change any logic, cryptography, or data handling, and there is no indication it fixes a security bug.

This commit is purely cosmetic: it reorders two 'extern crate' declarations 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 adds new test cases for existing decoder code. It checks that various decoders correctly report an error when their input data ends unexpectedly. No production code was changed, so there is no direct security fix or vulnerability introduced here.

This commit simply moves existing unit tests from one test file to another. No production code was changed, and no bug fix or security improvement was introduced. It is a routine code organization change.

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