rust-bitcoin

This commit removes an unused error category from a Bitcoin cryptography library. It is a cleanup change because the underlying signature-parsing code can no longer fail in the way that error category described. There is no direct evidence this fixes an active security bug, but it does slightly reduce the library's public error surface, which can help downstream code handle errors more reliably.

This commit is a routine code-quality refactor. It introduces new, more specific Rust error types for parsing keys and signatures, replacing a generic underlying library error type. There is no change to cryptographic behavior, validation logic, or security boundaries. It only changes what kind of error message callers receive when parsing fails.

This commit only updates generated API snapshot files (text listings of public functions) for the consensus_encoding crate. It adds entries for three new public functions that decode data using an explicit decoder type. There is no source code change, no bug fix, and no security relevance visible in the diff.

This commit adds new public helper functions to a Rust Bitcoin encoding library. The functions let callers decode data using a decoder type directly, rather than only through types that implement a specific trait. It is a pure API convenience addition and does not change existing behavior or fix any bug.

This commit adds a new helper function to the rust-bitcoin library that lets developers decode data from a reader using any decoder type that can be created with default settings. It is a pure API addition: it refactors an existing function into a shared internal helper and exposes a new public entry point. There is no bug fix, behavior change, or security-related content in the diff.

This commit removes a convenience conversion that let users turn a borrowed Taproot signature into an owned, serialized byte form. The change is API-cleanup: the old trait made it look like the serialized form was just a view of the original signature, when it actually copies/owns the bytes. There is no direct security bug fixed here, but removing the misleading conversion reduces the chance that future callers misunderstand ownership and accidentally clone or mishandle signature data.

This is an automated code-formatting commit from rustfmt. It only changes whitespace, line breaks, and adds a missing semicolon after a return statement. There is no functional change and no security relevance.

This commit is purely a housekeeping release step. It bumps the version number of the bitcoin-key-expression crate from 0.0.0 to 0.1.0, updates the changelog, and adjusts the main bitcoin package and lock files to match. There are no code changes, bug fixes, or security patches in the diff.

This commit simply bumps the version number of a CI linting tool (cargo-semver-checks) used in GitHub Actions from 0.47.0 to 0.48.0. It changes one line in a workflow configuration file and has no effect on the actual Bitcoin library code that users run.

This commit adds standard Rust trait implementations that allow certain Bitcoin signature-hash error types to be created from the Infallible type. Infallible is a type that can never actually exist, so these conversions can never be invoked at runtime. The change is purely an ergonomic improvement for generic programming and has no security relevance.

This commit reduces the visibility of internal fields on three error types in the crypto/sighash module from public to crate-internal. It is a routine API-hardening change to preserve future flexibility before a 1.0 stable release. There is no security vulnerability here.

This is a routine automated update that changes one version number in a project configuration file, bumping the recommended stable Rust compiler from 1.95.0 to 1.96.0. There is no code change and no security-relevant content.

This commit tightens validation for Bitcoin P2P message command strings. Previously, a command string could contain a null byte in the middle followed by more characters (for example "And\0rew"). Such malformed strings are now rejected both when created from Rust code and when received from the network. This prevents odd or potentially dangerous command strings from being accepted as valid.

This commit adds the ability to print a Bitcoin transaction witness as a hexadecimal string, mirroring functionality already available for other types. It is a routine feature addition with no security relevance visible in the code or commit message.

This commit only edits the project's changelog file (CHANGELOG.md). It adds historical release notes for versions 0.32.9, 0.32.10, and 0.32.100, and updates comparison links. No source code, build scripts, tests, or dependencies were changed. It is a documentation-only commit and does not alter program behavior or fix any vulnerability directly.

This commit only edits changelog files. It fixes Markdown link formatting, corrects a few typoed pull request numbers, updates release heading levels, and adjusts version compare links. No program code was changed, so it cannot introduce or fix a security vulnerability in the software itself.

This commit reorganizes how an optional hex-encoding helper library is enabled in the bitcoin-crypto crate. It makes the hex-conservative dependency optional and gated behind a new 'hex' feature, instead of being included by default. The main bitcoin crate explicitly enables this feature, so end-user behavior is unchanged. This is a build/configuration cleanup, not a fix for an exploitable vulnerability.

This commit only updates a generated text file that lists the public API surface of the crate. It adds entries for new public types and functions (a hex encoding/decoding error type and helper functions). There is no actual code change, no bug fix, and no security relevance visible in the diff.

This commit adds a new public helper function that lets users decode Bitcoin consensus data directly from a hexadecimal string, without needing to allocate a temporary byte vector. It is a pure feature addition: it introduces a new error type, exports the function under a feature flag, and includes unit tests. There is no indication in the commit that it fixes a security bug or that the change itself creates one.

This commit adds new convenience functions that let users convert Bitcoin consensus data into hexadecimal text strings. It is a pure feature addition: it does not change existing behavior, fix a bug, or alter any security-critical logic. There is no indication this commit addresses a vulnerability.

This commit simply moves a test from one file to another. It fixes a packaging problem where published source code would contain a broken unit test because a required data file was not included in the published package. There is no security issue in the code itself.

This commit removes leftover configuration entries that allowed duplicate references to a helper package called 'hex-conservative' in four sub-project files. It is a routine cleanup of stale build-tool metadata and does not change any executable code, dependencies, or security behavior.

This change fixes a memory allocation quirk in how Bitcoin transaction witness data is decoded. Previously, when reading a witness element, the decoder would reserve memory equal to the full claimed size of the element immediately, even though no actual element bytes had been read yet. The patch makes it reserve only a small minimum amount and let the buffer grow as real data arrives. This reduces the risk of an attacker causing large memory reservations by supplying a misleading length prefix, though the actual allocation still cannot exceed a built-in maximum.

This commit only fixes wording in an automated GitHub Actions workflow. It changes the pull request title and branch name from 'daily' to 'weekly' because the job actually runs once a week, not once a day. There is no code change, no security fix, and no vulnerability.

This commit only renames a long crate name to a shorter alias inside test files. It does not change any real program code, behavior, or security properties. There is no security issue here.