rust-bitcoin

This is a small test-only change that swaps one internal encoding helper for another inside the BIP152 test module. It does not touch production code, network handling, or consensus logic, and there is no indication it fixes or introduces a security issue.

This is a small test-only change that swaps out one internal encoding helper for another equivalent one inside unit tests. It does not touch production code, network handling, or any behavior visible to users.

This commit is a routine Rust crate maintenance change. It makes several underlying libraries publicly visible from the taproot-primitives crate root so that downstream users can refer to those types more conveniently. There is no security issue here.

This commit is a routine cleanup that removes an unused dependency called bitcoin-io from the crypto crate. It only touches package metadata and lock files, not any code that handles keys, signatures, or user data. There is no security issue visible in this change.

This commit removes convenience methods for reading and writing public keys from/to byte streams in the rust-bitcoin crypto crate. It is a routine API cleanup to reduce dependency on the bitcoin-io crate, not a security fix. There is no evidence in the commit or supplied references that this change addresses a vulnerability.

This commit only updates three generated API text snapshot files to reflect that a function now takes a mutable reference to its engine argument instead of taking ownership. There is no actual source code change in the commit, and nothing in the commit message or diff indicates a security issue.

This is a routine internal API cleanup in the rust-bitcoin hashing library. A helper function that feeds data into a hash calculator is changed so callers pass in the calculator by mutable reference instead of handing it over and getting it back. No security vulnerability is present in the diff; it is a usability and ownership-style refactor.

This commit fixes a spelling mistake in an error message: 'emoty' was corrected to 'empty'. It does not change any program logic, behavior, or security properties.

This change only updates the project's mutation-testing configuration file. It tells the cargo-mutants tool to skip generating certain test mutants for encoding/decoding methods because those artificial mutations would make the test suite hang. It does not change any production code, protocol behavior, or security-relevant logic.

This commit only adds new test code. It introduces a fake test-only Merkle node type so the project's mutation-testing tool can exercise a default trait method that real node types override on common CPU platforms. There is no change to production code, no bug fix, and no security-relevant behavior change.

This commit adds a new performance optimization for SHA-256 hashing on modern x86 processors. It introduces a code path that processes four blocks at once using SSE4.1 instructions when available. There is no indication in the commit that this fixes a security vulnerability; it appears to be a routine performance improvement.

This commit is a code cleanup in the Bitcoin library's SHA-256 hashing code. It replaces roughly 1,000 lines of manually repeated calculation steps with a few short macros that generate the same steps automatically. The author explicitly calls it a refactor with no behavior change, and the constants and arithmetic operations appear unchanged.

This commit adds a new, faster way to calculate SHA256d hashes for 64-byte inputs on modern Intel/AMD processors using SSE4.1 CPU instructions. It is a pure performance optimization and does not appear to fix or introduce a security vulnerability based on the code shown. However, because it is new cryptographic code, any bug in it could in principle produce wrong hash results, which would be a correctness issue rather than a direct security flaw.

This is a build-system fix for a Rust crate that supports both memory-allocator and no-allocator environments. The crate was always pulling in the standard memory allocator even when a user explicitly requested a no-allocator build, which would cause compilation to fail on platforms without an allocator. The patch simply adds the correct on/off switch so the allocator is only used when the corresponding feature is enabled. There is no runtime security vulnerability or exploit here.

This commit is a feature-gating cleanup, not a fix for an active security flaw. The taproot-primitives crate was always enabling hex (base-16 string) support for its hash types, even when downstream users did not ask for it. The change adds an explicit 'hex' feature, turns it off by default, and makes the bitcoin crate request it explicitly. This gives users more control and avoids pulling in unneeded functionality, but it does not patch a vulnerability that can be directly exploited.

This commit only changes documentation wording for a Rust Bitcoin data type. It adds a note that the serialized legacy public key type avoids heap allocation and has a maximum size of 65 bytes. No code behavior was altered.

This commit removes two helper methods that wrote ECDSA signatures to a custom I/O writer. It is a straightforward API cleanup to drop a dependency, not a security fix. There is no evidence of a vulnerability being patched.

This commit is a small internal cleanup in the rust-bitcoin library. It stops using a PSBT-specific deserialization helper to build test-only 'Arbitrary' instances of TapTree, and instead builds the tree directly from its internal NodeInfo. It also switches serde derives to use the proper serde::Deserialize trait. There is no direct evidence this fixes an exploitable security bug, but it removes a confusing and potentially incorrect reuse of PSBT serialization logic outside the PSBT module.

This commit adds Rust compiler hints (#[must_use]) to five small helper functions that simply convert numbers from one type to another or create an empty container. The change only produces new compiler warnings when a caller ignores the returned value; it does not change how any existing code behaves at runtime and does not fix an active security bug.

This commit only fixes minor style warnings reported by the Clippy linter. It changes how a file path is printed in a build script, adds a missing semicolon in a hashing function, removes an unnecessary semicolon after an if block, and replaces one numeric type cast with a safer conversion in a unit test. None of these changes fix a security vulnerability.

This commit adds new encoding and decoding logic for Bitcoin P2P v2 network messages in the rust-bitcoin library. It is a feature/refactoring change that introduces a new way to serialize and deserialize v2 protocol messages. There is no direct evidence in the commit that this fixes a known security vulnerability, but any new parser for network-facing data is a potential source of bugs such as crashes, denial of service, or memory issues if it mishandles malformed input.

This commit is a pure code cleanup in the rust-bitcoin library's 'units' module. It reorders where encoder and decoder definitions appear in six source files so that the Encodable and Decodable trait implementations come before the macro-generated encoder/decoder structs. No behavior, logic, or security properties change; it only makes the layout consistent.

This commit only adds new unit tests for existing script types in the rust-bitcoin library. It does not change any production code, fix bugs, or alter behavior. There is no security relevance.

This commit only adds an extra test line to verify that a Bitcoin hash type can be borrowed as a byte slice. It is a routine test-coverage improvement with no functional code changes and no security relevance.

This commit only changes test code. It updates two existing tests that check error handling for oversized Bitcoin scripts, making the assertions more robust by verifying the error is non-empty and has no underlying cause. There is no change to production code and no security fix or vulnerability introduced.