rust-bitcoin

This is a routine code cleanup that renames the type `DerivationPath` to `RelativeDerivationPath` throughout the project. The change is purely a refactor: it does not alter how the code behaves, what it computes, or how it handles data. The commit message explicitly says the rename is intended to force other developers to update their code so the maintainers can identify places that may later need a new `AbsoluteDerivationPath` type. There is no security fix or vulnerability here.

This commit refactors how Bitcoin BIP-32 derivation paths are represented in the rust-bitcoin library. It splits the old single DerivationPath type into two: DerivationPath (relative paths like 0'/1) and AbsoluteDerivationPath (master-prefixed paths like m/0'/1). The goal is to make wallet code more explicit about whether it is deriving from the master key or from an intermediate key. The change is a type-system/API hardening, not a fix for a known exploitable bug. It may prevent future misuse where a relative path is accidentally treated as absolute or vice versa, but the commit itself does not describe any active vulnerability.

This commit is a simple rename of a method from 'extend' to 'join' in a Rust Bitcoin library. It does not change what the code does, only its name. There is no security issue here.

This commit is a routine version bump for the bitcoin-units crate from 0.3.0 to 0.4.0. It updates version numbers in package manifests, lock files, and adds a changelog entry describing new features and breaking changes. There is no code change that fixes or introduces a security issue.

This commit only updates a configuration file used by an automated mutation-testing tool. It tells the tool not to waste time trying to mutate a very simple default method called `is_empty` on an encoder type. There is no change to actual library code, no bug fix, and no security relevance.

This is a tiny code cleanup in the Bitcoin peer-to-peer networking code. It replaces a slightly more verbose way of stripping trailing null characters with a simpler, equivalent way. There is no security impact.

This is a small internal code cleanup in a Bitcoin library. It splits one function into two so the inner logic doesn't have to be repeated, but the public behavior is unchanged. There is no security issue visible in the change.

This commit only refreshes automatically-generated API snapshot text files. It adds lines documenting two already-existing ArrayVec methods (set_len and spare_capacity_mut) and reorders one existing method. No source code, logic, or behavior changed, so there is no security impact.

This is a minor code cleanup for an error type in the BIP-32 (Bitcoin key derivation) module. It adds a standard 'Copy' trait, a conversion from Rust's 'Infallible' type, an explicit 'no underlying cause' implementation, and slightly clarifies an error message. There is no security fix or behavior change.

This commit adds a standard Rust equality trait (Eq) to the Bip32Seed type. It is a routine, non-functional change that does not alter behavior, fix a bug, or address any security issue. There is no security relevance.

This commit only changes a GitHub Actions CI workflow to reduce how much log output is printed during automated testing. It sets an environment variable named RBMT_LOG_LEVEL to 'progress' so the CI logs are shorter but still readable. There is no change to the actual Bitcoin library code, no security fix, and no vulnerability.

This commit fixes a low-level memory-safety issue in the SHA-256 code that runs on ARM 64-bit processors (aarch64). The code was asking the CPU to load four 32-bit numbers starting from a pointer that only pointed to a single 32-bit number. Rust's strict memory rules (flagged by the Miri checker) consider this undefined behavior, even though real hardware often tolerates it. The fix uses a pointer to the whole array instead, so the load is clearly valid.

This commit only reformats the wording and layout of multiple CHANGELOG.md files. It adds a top-level 'Changelog' heading, converts release headings from H1 to H2, adds an 'Unreleased' section, and appends Markdown link references that point to git tags or comparison URLs. No program code, build scripts, dependencies, or documentation that affects behavior were changed. There is no security relevance.

This commit simply deletes the top-level CHANGELOG.md file from the rust-bitcoin repository. The file only contained links to per-crate changelogs and was not executable code, configuration, or documentation that affects security. There is no security relevance.

This commit only removes two sections from a README file in the hashes subcrate: one about setting up git hooks and one about running benchmarks. No code, build scripts, tests, or documentation about cryptographic behavior were changed. There is no security relevance.

This commit is purely a maintenance update to the project's continuous integration (CI) tooling. It upgrades an internal helper tool called cargo-rbmt and regenerates large API snapshot files because the new version produces cleaner, de-duplicated output. No actual Bitcoin library code was changed, and there is no security relevance.

This commit only fixes broken or missing backticks in documentation comments within two example files. It changes how Rustdoc links and formats text, with no effect on actual program behavior or security.

This commit is a straightforward code cleanup in the rust-bitcoin library. It removes top-level imports of serde serialization traits and replaces them with explicit `serde::` prefixes in the key module. There is no functional change to how keys are serialized or deserialized, and no security issue is introduced or fixed.

This commit is a routine API cleanup in the rust-bitcoin library. It renames a public key serialization method from `to_bytes` to `serialize`, restores `to_bytes` as a deprecated alias that returns a plain byte vector, and updates internal callers to use the new name. There is no security fix or vulnerability here.

This commit is a straightforward internal code reorganization. It takes a single large module named 'encapsulate' in the cryptographic key code and splits it into several smaller modules, one for each key type. The public types and their behavior remain exactly the same; only the internal file/module structure and re-export paths changed. There is no security fix or vulnerability here.

This commit fixes a bug in how the Bitcoin witness data decoder grows its internal buffer. Previously, when decoding witness data, the code could fail to reserve enough space before writing a size value, causing the program to panic and crash. The fix ensures the buffer is always expanded by at least a minimum amount when free space is low.

This commit only fixes the formatting of a documentation link. It changes 'BIP-340' to 'BIP-0340' and wraps the URL in angle brackets so it renders correctly in Rust's generated documentation. No code behavior was changed, and there is no security impact.

This commit is a simple variable rename from 'pk' to 'key' in two Rust functions because 'pk' is commonly understood to mean public key, while the parameter is actually a private key. There is no change to program logic, no security fix, and no behavior change.

This commit only adds new automated tests that check error types implement certain standard Rust traits (Display and From<Infallible>). It does not change any production code, fix a bug, or alter behavior. There is no security relevance.

This commit only adds a new automated test to the codebase. It does not change any production code. The test verifies that a Bitcoin block containing a fake witness commitment but missing the required reserved value is correctly rejected by existing validation logic. There is no security fix or vulnerability being introduced here.