rust-bitcoin

This commit is a routine automated code-formatting run by the rustfmt tool. It only changes whitespace, import order, and brace style in five files. There are no functional code changes, no bug fixes, and no security-related alterations.

This change is a routine code cleanup, not a security fix. It removes an overly broad feature gate so that parts of the Taproot cryptographic module are available even when the optional 'alloc' feature is disabled, while keeping functions that actually need memory allocation behind the gate. There is no indication it fixes a vulnerability.

This commit is a small internal cleanup in the rust-bitcoin library. It changes how a Taproot signature is parsed from a hexadecimal string so that it no longer needs to allocate a temporary byte vector. The change removes an unnecessary memory allocation but does not alter the allowed signature formats or fix any vulnerability. It is a performance and dependency-reduction refactor, not a security fix.

This commit is a routine dependency cleanup. The project previously had to use two different versions of the same hex-encoding helper library (one stable, one unstable preview) because a needed feature was only available in the unstable version. Now that the stable library released version 1.1.0 with that feature, the commit removes the unstable dependency and switches everything to the single stable version. It is not a security fix and does not change how the software behaves to users.

This commit removes one line from a generated API text file that lists public re-exports. The removed line was for an unstable/internal feature re-export (`hex_unstable`). There is no code change, no security fix, and no functional behavior change. It is purely a documentation or generated-file maintenance update.

This commit fixes a bug in how Bitcoin peer-to-peer network messages are validated. The software was checking message checksums against a re-encoded version of the message payload rather than the original bytes received over the network. Because the protocol allows some wiggle room in encoding, a re-encoded payload can have a different checksum than the original raw bytes. This meant a malformed message could pass checksum validation when it should have been rejected. The fix computes the checksum directly from the raw bytes as they arrive, removing that ambiguity.

This commit only adds a new unit test. It does not change any production code. The test checks that a malformed Bitcoin P2P v1 message with a non-standard boolean encoding and a bad checksum is correctly rejected. Because no actual code behavior is changed, this commit by itself does not fix or introduce a security issue.

This commit adds support for a new Bitcoin peer-to-peer message type called `sendtxrcncl` (transaction reconciliation, part of the Erlay protocol). It is a routine protocol feature addition: it wires up encoding and decoding for the new message so the library can send and receive it. There is no indication in the commit of a security bug, fix, or vulnerability.

This commit adds support for decoding a new Bitcoin peer-to-peer network message called 'sendtxrcncl', which is part of an upcoming feature called Erlay. It does not change any existing behavior; it simply lets the library recognize and parse this message type. There is no indication this introduces a security problem.

This commit fixes a fuzz test (an automated correctness test) in the rust-bitcoin project. The test previously compared raw input bytes to re-serialized JSON bytes, which can fail for harmless reasons like whitespace or key ordering. The fix compares the parsed Rust data structures instead, which is the correct way to verify round-trip behavior. This is a test-only change and does not affect any production code or user-facing behavior.

This commit adds a standard trait implementation that lets the Hmac type be used with property-testing tools. It is a routine feature addition, not a security fix or vulnerability.

This commit adds a new automated fuzz-testing target for the project's hash types. It does not change any production code, fix a bug, or alter behavior visible to users. It is purely a testing/infrastructure addition.

This commit is a routine code cleanup in the rust-bitcoin library. It replaces several hand-written loops that serialize lists of values with a single standard helper called collect_seq. There is no functional change intended, and nothing in the commit suggests a security fix or vulnerability.

This commit is a performance improvement for internal fuzz testing code. It removes an unnecessary memory allocation when testing that data can be encoded and decoded correctly. There is no security vulnerability or fix here.

This commit narrows the visibility of internal helper methods named to_inner on Bitcoin public-key types. Previously any outside code could call these methods to extract the raw underlying secp256k1 key objects; now only code inside the same module can do so. This is a defensive encapsulation change that reduces the public API surface and makes future misuse or accidental exposure of internal cryptographic details less likely. It is not a fix for an active vulnerability.

This commit is a routine API cleanup in the rust-bitcoin crypto library. It removes a method called as_inner that returned a reference to the underlying key data, and replaces internal uses with to_inner, which returns the key by value. The underlying key type is small and cheap to copy, so this is a consistency improvement, not a security fix. There is no indication this change addresses a vulnerability.

This commit only changes the capitalization of hash algorithm names in comments and documentation strings (for example, 'sha256' becomes 'SHA256' and 'sha256d' becomes 'SHA256d'). No program logic, code behavior, or security properties were modified.

This commit only fixes typos and formatting in documentation comments and test file comments. No code behavior changes.

This commit removes an unused internal dependency called bitcoin-crypto from the taproot-primitives crate. It only changes package metadata and lock files; no actual code is modified. There is no security issue here.

This commit is a routine code reorganization. It moves one function, `from_key_and_merkle_root`, out of a low-level crate (`taproot-primitives`) and into a higher-level crate (`bitcoin`) as an 'extension trait.' The goal is to remove an internal dependency so the low-level crate can stabilize sooner. The actual computation performed by the function is unchanged.

This commit only adds a test file containing fully commented-out code. It documents that certain hashing traits in the library are not 'dyn compatible' (a Rust technical term meaning they cannot be used as trait objects). No actual code behavior changes, no bug is fixed, and no security issue is introduced.

This is a tiny code cleanup in a Rust hashing library. It removes an unnecessary `.clone()` call because the underlying data type can be copied automatically. There is no security issue here.

This commit only adds two missing changelog entries to a documentation file (hashes/CHANGELOG.md). It records that previous point releases removed a documentation configuration flag called `doc_auto_cfg`. No code, build scripts, tests, or dependencies were changed. There is no security relevance.

This is a routine internal refactoring commit in the rust-bitcoin project. It removes a direct dependency on the main 'bitcoin' crate from the smaller 'p2p' (peer-to-peer messages) crate and instead pulls in the needed features from more focused sub-crates. The only code change is updating a documentation example to use a different decoding function. There is no security-relevant change visible in the diff.

This commit is a purely cosmetic code-style change. It rewrites some Rust feature-gate conditions from one allowed syntax to another preferred syntax, with no change to which features enable which code. There is no security relevance.