rust-bitcoin

This commit only adds a new automated test that checks the Debug text representation of two public error types is never empty. It does not change any library code, fix a bug, or alter behavior. There is no security issue in the diff itself.

This commit only adds a new automated test that checks two existing error types implement Rust's standard Error trait. It does not change any production code, fix any bug, or alter behavior. There is no security relevance.

This commit only adds two lines to a test file, checking that a type called Hkdf can be safely used across threads (Send/Sync). It is purely a test-coverage improvement with no changes to production code, no bug fixes, and no security-relevant behavior changes.

This commit is a routine dependency and API cleanup in the rust-bitcoin project's hashing crate. It swaps an unstable hex-parsing helper for a newly released stable version and updates the error types that downstream code sees. There is no direct evidence of a security vulnerability being fixed; it is best understood as a maintainability and API-stability improvement.

This commit is a routine internal cleanup in the rust-bitcoin project's peer-to-peer (p2p) crate. It swaps some test and internal code from using an unstable version of a hex-encoding helper library to a newly released stable version. There is no user-facing behavior change, no bug fix, and no security fix visible in the diff.

This commit is a routine internal cleanup in the rust-bitcoin library. It swaps one hex-decoding helper for another equivalent one so the library no longer depends on an 'unstable' public API from a dependency. There is no indication this fixes a security bug or changes behavior visible to users in a dangerous way.

This commit swaps out an unstable, experimental hex-decoding helper for a stable, project-owned one. It is a cleanup/refactoring change to keep the public API from depending on a crate version that is not yet finalized. There is no direct security bug being fixed; the main risk is that if done incorrectly, error handling could change slightly for users parsing hex strings.

This commit is a trivial documentation punctuation fix. It adds a missing full stop to a rustdoc comment in an internal macros file. There is no code change and no security relevance.

This commit only reformats documentation comments (rustdocs) so they wrap at 100 characters per line. It changes line breaks and spacing in comments only, with no changes to actual code logic, APIs, or behavior. There is no security relevance.

This commit changes a single line of documentation in the source code, adding a '#' character so that the crate's title displays as a proper heading in generated documentation. It has no effect on program behavior, security, or functionality.

This commit only adds a missing software license comment (CC0-1.0) to a test file. It does not change any code behavior, fix any bug, or alter any security-relevant logic.

This commit adds a missing documentation attribute to a public type alias in the rust-bitcoin hashes library. It only affects how the SHA3-256 hash type appears in generated API documentation and has no security or runtime effect.

This commit changes how a Bitcoin library decodes byte slices. Previously, a function called decode_from_slice silently accepted extra bytes after a valid object. Now it rejects leftover bytes, and a new function decode_from_slice_unbounded is provided for cases where callers intentionally want to read only part of the input. This is a defensive correctness fix that prevents accidental acceptance of malformed or padded data, but it also changes the public API behavior and error types, which could break downstream code.

This commit adds optional serialization/deserialization support (via the serde library) for two data types, FilterHash and FilterHeader, used in Bitcoin peer-to-peer compact block filters. It is a routine feature addition, not a security fix or vulnerability patch. There is no indication of a security issue in the code changes themselves.

This commit only updates a generated text file that lists the public API surface of the crate. It adds entries for new serde helper functions that support vectors of amounts and fee rates. There is no source code change, no bug fix, and no security relevance visible in the diff.

This commit adds new Rust code that lets programs serialize and deserialize lists (vectors) of Bitcoin amounts when using the serde data-format library. It is a feature addition with matching tests. There is no indication it fixes a security bug or introduces a vulnerability.

This commit adds new serialization/deserialization helpers so that a list of Bitcoin fee-rate values can be converted to and from JSON (or other serde formats). It is a straightforward feature addition with matching unit tests and contains no security fix or vulnerability.

This commit only moves existing code around in the same file. It takes several implementation blocks for the Hmac type and places them directly below the Hmac struct definition instead of further down after another struct. No code behavior, logic, or public interface was changed.

This commit simply moves existing code around in two files. It relocates the implementation blocks for SHA256 and SipHash24 hash types to appear earlier in their respective files, right after the hash type is declared. No code behavior was changed, no bugs were fixed, and no security issues were introduced.

This commit only updates a test-tool configuration file. It tells an automated mutation-testing tool (cargo-mutants) to skip testing certain code patterns because they would cause the test suite to loop forever. It does not change any actual library code, fix a bug, or alter how the software behaves in production.

This commit is a routine code cleanup. It replaces four hand-written formatting rules for the CompactTarget type with a single existing macro that does the same thing. There is no functional change and no security relevance.

This commit adds compiler hints (#[inline]) to formatting functions for some numeric wrapper types. It is a routine performance/cleanup change and does not alter program behavior or fix any security issue.

This commit only updates generated API snapshot text files so they reflect that a type named TxMerkleNodeDecoder was moved from the transaction module to the merkle_tree module. No actual source code, logic, or behavior changed. It is a bookkeeping change to keep automated API checks in sync with a previous code reorganization.

This commit is a straightforward code organization change. It moves where two helper types (TxMerkleNodeDecoder and TxMerkleNodeDecoderError) are publicly exported so they sit alongside related types in the merkle_tree module instead of the transaction module. There is no change to how data is decoded, no bug fix, and no security impact.

This commit swaps out a custom hex-decoding helper for a simpler one in the code that turns serialized data back into Bitcoin witness structures. The change is driven by an upstream library hiding its internal error details, not by a known security flaw. The main practical effect is that error messages become less specific when someone feeds in bad hex data. There is no direct evidence this introduces a vulnerability, but it slightly weakens defensive error reporting.