rust-bitcoin

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 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.

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 adds new unit tests for the existing hexadecimal encoding/decoding code. It does not change any production logic, so it cannot introduce or fix a security vulnerability on its own.

This commit is a simple internal code reorganization. It moves the SerializedLegacyPublicKey type from the main bitcoin crate into the lower-level crypto crate and re-exports it so existing code keeps working. No behavior changes, no bug fixes, and no security implications are visible in the diff.

This is a small internal code cleanup in the rust-bitcoin library. It changes how one public-key wrapper type exposes its underlying byte slice, removing a dependency on another type (PushBytes) so the code can be moved between crates more easily. There is no user-visible behavior change and no security fix.

This commit only updates version numbers and pinned commit hashes for GitHub Actions used in the project's automated CI (continuous integration) workflows. It does not change any of the actual Bitcoin library code that users or applications interact with. There is no indication of a security vulnerability being fixed or introduced.

This commit only updates automatically-generated API snapshot files. It shows a public type being renamed from EncodableByteIter to EncoderByteIter and changing from borrowing an encodable value to owning an encoder. There is no source code change in the diff, no bug fix, and no security-relevant behavior shown.

This is a routine internal refactoring of a Rust Bitcoin library type. It renames EncodableByteIter to EncoderByteIter and changes it to wrap an encoder directly rather than an encodable value. There is no security fix or vulnerability indicated in the commit.

This is a routine code cleanup commit that fixes two Rust lint warnings in the taproot-primitives crate. It adds a Clippy suppression annotation and replaces an integer cast with a safer conversion. There is no security-relevant behavior change.

This commit is a routine code reorganization: it moves Taproot hash types (like TapLeafHash, TapNodeHash, TapTweakHash) and the LeafVersion enum from the main bitcoin crate into a new taproot-primitives crate. The bitcoin crate then re-exports these types so existing users see no change. There is no security fix or behavior change visible in the diff.

This commit is a routine internal code reorganization. It moves some Taproot hash helper methods from direct implementations on two types into Rust 'extension traits' so the underlying types can live in a more basic crate while the extra logic stays in the main bitcoin crate. There is no change to what the code computes or any security behavior.

This commit creates a brand-new, empty Rust crate named 'bitcoin-taproot-primitives'. It contains no executable code, no new logic, and no changes to existing behavior. It is purely a project structure change preparing for future development.

This commit removes automatic error-conversion shortcuts in the crypto module of the rust-bitcoin library. It does not fix a bug or vulnerability; it is a deliberate API cleanup to avoid promising too much to future users. Existing code that relied on the removed conversions will need minor updates, but runtime behavior is unchanged.

This change simply re-exports a few internal Rust crates through the public API of the `crypto` sub-crate so users don't have to add those dependencies manually. It is a routine dependency-management and API-ergonomics patch with no apparent security relevance.

This commit simply makes several existing key types easier to import by re-exporting them at the top level of the crypto crate. It does not change any behavior, logic, or security properties of the code.

This commit simply moves existing transaction encoding and decoding tests from one file to another. It does not change any production code, only reorganizes test code. The only functional tweak is replacing one detailed error comparison with a broader pattern match, because the moved test can no longer see a private inner error type. There is no security issue here.

This commit is a large but straightforward internal code reorganization. It moves Bitcoin key types (public keys, private keys, keypairs, and related errors) from the main `bitcoin` crate into a new `crypto` sub-crate, then re-exports them so existing users of the `bitcoin` crate see the same public API. There is no indication of a security bug being fixed or introduced; it is a refactoring to improve the project's modular structure.