rust-bitcoin

This commit is a routine code cleanup in the rust-bitcoin library. It moves an error type related to decoding Bitcoin block timestamps into a new 'error' submodule and re-exports it. There is no change to how the code behaves, no bug fix, and no security improvement or vulnerability introduced.

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 existing error type definitions into a new 'error' submodule and re-exports them so they remain accessible from the same public locations. There is no change to how numbers are parsed, no change to public behavior, and no security relevance.

This commit is a routine internal code reorganization. It moves an error type (CompactTargetDecoderError) from one place in the source file to a new 'error' submodule and re-exports it so existing code keeps working. There is no functional change to how the library behaves, and no security issue is present.

This commit is a routine code reorganization. It moves two error type definitions from the main block module into a new 'error' submodule and re-exports them so existing code continues to work. There is no functional change to how the library behaves, and no security issue is present.

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 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 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 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 only updates generated API text files that list the public surface of the Rust crate. It reflects that some types (merkle-tree and transaction ID types) were moved into different modules, but it does not change any source code, logic, or behavior. There is no security issue here.

This is a trivial code cleanup change. It replaces one way of referring to a type (`crate::Wtxid`) with a direct import (`Wtxid`). The program's behavior is unchanged, and there is no security relevance.

This is a tiny internal code cleanup change. It swaps one way of importing a type (Wtxid) for another equivalent way within the project's own test code. There is no functional change, no bug fix, and no security relevance.

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 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 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 removes an unused compiler hint (`#[macro_use]`) from a module declaration. It is a routine code cleanup with no functional or security effect.

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.