rust-bitcoin

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.

This commit simply moves existing unit tests from one internal crate to another and rewrites them to use a newer encoding API. No production code behavior changes, and no security bug is fixed or introduced.

This commit only fixes code style issues (lint errors). It adds underscores to large number literals and replaces a closure with a direct function reference in test code. There is no change to security-sensitive behavior.

This commit simply moves existing unit tests from one crate to another within the same project. No production code behavior is changed, so it has no security impact on users of the library.

This commit simply deletes a duplicate unit test from one crate because the same test already exists in an upstream crate. It does not change any production code, behavior, or security properties.

This commit is a routine code reorganization: it moves a set of existing tests from one crate to another and removes an empty test module. No production code, APIs, or security behavior changed.

This commit only fixes code style and documentation warnings (lint errors) in the key-expression crate. It adds missing documentation comments, marks some functions with #[must_use], rewrites number literals with underscores, and makes minor test helper signature changes. There is no change to runtime behavior or security logic.

This is a minor internal code cleanup in a Rust formatting helper. It changes one function from borrowing a small value to copying it, following a common Rust style suggestion. There is no security relevance.

This commit only adds documentation text to a Rust macro. It explains when a hex-string parsing function can fail. No code behavior changed, and there is no security issue in the patch itself.

This commit is a routine code reorganization: it moves the BIP-32 (hierarchical deterministic wallet key) module from the main `bitcoin` crate into a new lower-level `key-expression` crate, then re-exports it so existing users of `bitcoin::bip32` see no change. There is no evidence in the commit of any security bug, vulnerability fix, or behavior change.

This is a trivial code cleanup: a developer replaced a wildcard import (`use super::*`) with a single explicit import (`use super::SerializedSignature`) in a small internal module. It has no security relevance; it only makes the code clearer and silences a Clippy lint.

This is a one-word documentation comment fix. It changes an incorrect reference to 'ARM SHA2 intrinsics' to the correct 'x86 SHA-NI intrinsics' in a code comment. No executable code was changed, and there is no security impact.

This commit is a routine performance optimization for SHA-256 hashing on modern CPUs. It rewrites the inner loop so that multiple 64-byte blocks are processed in one go, keeping the calculation state in CPU registers rather than reloading it each time. The change is purely about speed and does not fix or introduce any security-relevant behavior.

This commit is an automated code-formatting run by the rustfmt tool. It only adjusts whitespace and line breaks in four source files, making no changes to program logic, algorithms, or data handling. There is no security relevance.

This is a small code cleanup in how Taproot signatures are printed or formatted as text/hex. It removes a tiny bit of duplicated logic by reusing an existing serialization helper and adds two new formatting traits (LowerHex and UpperHex). There is no security issue visible in the change.

This commit simply removes an unused library dependency (bitcoin-io) from the p2p crate after a newer encoding library made it unnecessary. There is no code change, no bug fix, and no security issue visible in the diff.

This commit only adds a new unit test for a bug fix that was already applied in the previous commit. It does not change any production code itself. The test verifies that a Taproot signature can be serialized back to the same hex string it was parsed from. Because the actual fix happened earlier, this commit alone does not introduce, fix, or worsen any security issue.

This commit fixes a crash when printing or formatting a Taproot serialized signature. The old code assumed every signature was the maximum possible length, but real signatures can be shorter. When a shorter signature was formatted, the code could panic or crash. The fix checks the actual length and formats with the correct size.

This is a tiny internal code cleanup. It changes how a network 'magic' number is printed on screen so that one formatting routine reuses another identical routine, instead of duplicating the same logic. There is no security relevance.

This commit is a pure code-style refactor. It rewrites two small functions in the relative locktime module to use Rust's functional method chaining instead of 'if let' and 'match' blocks. The behavior is unchanged: the same inputs produce the same outputs, and no security-sensitive logic was added or removed.