rust-bitcoin

This commit only moves existing tests from one crate to another and adds new unit tests for script helper functions. It does not change any production code behavior, so it has no security impact on its own.

This commit is a simple code reorganization: two helper functions for working with OP_RETURN outputs are moved from one internal module to another. The actual behavior of the functions is unchanged, and there is no security fix or vulnerability introduced.

This commit is a straightforward internal code reorganization. It moves a helper function called witness_version from one Rust module to another within the same project, without changing what the function does or how it behaves. There is no security fix or vulnerability here.

This commit is a routine internal code reorganization. It moves helper functions that identify and create common Bitcoin script types (like P2SH, P2WSH, P2WPKH, P2A) from the main `bitcoin` crate into the lower-level `primitives` crate. The actual logic of these functions is copied unchanged; only their location in the codebase changes. There is no indication this fixes or introduces a security vulnerability.

This commit is a routine internal code reorganization. It copies a small helper function that builds SegWit scriptPubkeys into a lower-level crate so both crates can use it. The function remains private to the library, performs no user-facing behavior changes, and adds no new public API or security-sensitive logic.

This commit simply copies a few internal Bitcoin script constants (specific byte values used in transaction scripts) into a lower-level crate module. It does not change any public behavior, fix a bug, or alter how data is validated. There is no security relevance visible in the change itself.

This commit only updates documentation comments and adds code examples for two Rust modules. No program logic, behavior, or security-sensitive code was changed. It is a documentation-only cleanup.

This commit is a straightforward internal code cleanup in the Bitcoin peer-to-peer message handling code. It replaces four separate fields (magic number, payload length, checksum, and the payload itself) with a single pre-existing 'message header' object that already contains those same values. No behavior changes are visible in the diff; it is purely a refactor to make the code structure match the standard Bitcoin protocol layout of header plus payload.

This commit changes two GitHub workflow files so that an automated bot updates the Rust compiler toolchain on both the master branch and a long-term support branch (0.32.x), instead of only on master. It is a routine CI/CD maintenance change with no security relevance.

This commit only changes the project's automated daily testing setup so that a verification tool called Kani also runs against an older long-term support branch (0.32.x) in addition to the main branch. It does not modify any library code, user-facing behavior, or security-sensitive logic. There is no indication this is a security fix or introduces a vulnerability.

This commit adds standard Rust conversion traits (From/TryFrom) between an ECDSA signature and its serialized byte form. It is a small API-consistency change that mirrors traits already present on the Taproot signature type. There is no indication it fixes a security bug or introduces a vulnerability.

This commit adds new ways to print ECDSA Bitcoin signatures as hexadecimal text (lowercase and uppercase), matching formatting already available for Taproot signatures. It also makes the existing Display implementation reuse the new LowerHex implementation. There is no security fix or behavior change that affects signatures themselves—only how they look when formatted as text.

This commit fixes a formatting bug in how Bitcoin ECDSA signatures are printed as text. Previously, the signature was printed in two separate pieces (the DER-encoded signature and the sighash byte), which could mishandle formatting options like width or precision. Now it prints a single pre-serialized object, so formatting behaves consistently. This is a correctness bug, not a cryptographic vulnerability, and there is no evidence it enables code execution or theft of funds.

This commit simply adds standard sorting traits (PartialOrd and Ord) to an ECDSA signature type and its associated sighash type, matching what already exists for similar types. There is no indication this fixes or introduces a security problem.

This commit is a routine API cleanup, not a security fix. It removes a helper trait called PrivateKeyExt and hides a low-level accessor method (as_inner) that exposes the underlying secret key object. The same signing behavior is preserved inside the crate, just with less public surface area. There is no patch for an active vulnerability.

This commit removes a deprecated type alias named `DerivationError` from the public API, replacing it with the already-existing `DeriveXpubError`. It is a straightforward cleanup with no functional code changes and no security implications.

This commit is a code cleanup: it splits one big error type into several smaller, more specific error types for BIP-32 extended key parsing. It does not change what the code accepts or rejects, only how errors are named and organized. There is no security fix here.

This commit is a pure code-style change. It reorders the implementation blocks for several error types in a Bitcoin-related Rust library so that the order of traits (From, std::error::Error, Display, helper methods) is consistent. No logic, behavior, or security properties of the code are changed.

This commit removes the old `bitcoin::consensus` module from the rust-bitcoin library because its functionality has already been replaced by a newer `consensus_encoding` module. It is a cleanup change that deletes unused code; no security vulnerability is introduced or fixed.

This commit simply deletes two unused internal constant definitions (SEGWIT_MARKER and SEGWIT_FLAG) from one source file because identical copies already exist elsewhere in the project. It is a routine code cleanup with no functional or security change.

This commit simply deletes an unused internal Rust macro called impl_consensus_encoding. The macro was only used to implement old Bitcoin consensus serialization traits, which are also being removed. There is no security issue here—this is ordinary cleanup of dead code.

This commit removes old serialization/deserialization trait implementations (called Encodable and Decodable) from many Bitcoin data types in the rust-bitcoin library. It is described by the project as a cleanup step toward replacing the old consensus encoding code. There is no indication in the commit or supplied references that this fixes a security vulnerability; it appears to be a routine internal refactor.

This is a small internal code cleanup in the rust-bitcoin library. It changes how transaction output (TxOut) objects are prepared for serialization so they use a dedicated wrapper type (TxOutEncoder) instead of directly combining two lower-level encoders. The commit message frames this as improving encapsulation, but the diff itself does not show any actual security bug, exploit path, or behavior change in the serialized output. It is best treated as a defensive maintenance patch.

This is a small internal code cleanup in the rust-bitcoin library. It changes how transaction input (TxIn) objects are prepared for serialization so they use a dedicated wrapper type (TxInEncoder) instead of a generic three-field encoder. The commit message frames this as better encapsulation, but the diff itself only shows a refactor with no change to the actual serialized bytes or to public behavior. There is no direct evidence of a security vulnerability being fixed.

This is a small internal code cleanup in the rust-bitcoin library. It changes how Bitcoin block objects are encoded to use a dedicated BlockEncoder wrapper instead of a generic two-part encoder. The actual bytes produced are unchanged; only the internal type structure is different. There is no security issue visible in the change.