rust-bitcoin

This commit only updates generated API snapshot files that list what types and functions are publicly exposed by the library. The actual code did not change; only the recorded API signatures were updated to reflect new type aliases (shorter names for encoder combinations). There is no security issue here.

This commit only updates an automatically generated API listing file. It reflects a change in how an error type is declared in the source code (from a public enum to a public struct wrapper), but the commit itself does not contain any actual code changes, logic changes, or security fixes. There is no indication this is a security patch.

This commit is a routine API design change, not a security fix. It renames an internal error enum and wraps it in a private struct so the library can keep the error type flexible before its first stable release. No vulnerability is patched and no exploit is possible.

This is a routine performance refactor. It swaps a slow, character-by-character hex formatting loop for one that writes whole chunks at a time. There is no security-relevant change.

This commit adds a small, harmless feature to a Rust Bitcoin encoding library. It lets an optional encoder report its length when it has a value, and report zero length when it is empty. There is no security issue here.

This commit swaps out an older Bitcoin data-encoding system for a newer one across six files. It is a routine internal refactoring change. There is no direct evidence in the commit that it fixes a security vulnerability, but any encoding change in consensus-critical code carries a small risk that a subtle behavior difference could affect transaction or block validation. The commit message and diff do not describe any security issue or credit a researcher.

This commit only updates internal fuzz-testing code to use a newer serialization API (consensus_encoding) instead of an older one being removed. It does not change the library's runtime behavior or fix any security bug.

This commit only changes test code and documentation examples in the rust-bitcoin library. It replaces older consensus encoding/decoding helper functions with newer equivalents from a different internal module. There is no change to production code, no bug fix, and no security-relevant behavior change.

This commit is a routine internal test refactor. It swaps one test-only helper for another so that a unit test can still decode hex transaction data after an older helper is removed. There is no change to production code or to how real transactions are handled.

This commit only updates example code in the rust-bitcoin project. It replaces older 'consensus' encoding/decoding API calls with newer 'consensus_encoding' API calls in three example files. There is no change to the library's actual security-sensitive code, no bug fix, and no security patch.

This commit adds a new convenience method, XOnlyPublicKey::verify, that lets users verify Schnorr (taproot) signatures without calling the underlying secp256k1 library directly. It is a straightforward API addition with no obvious security bug; it simply wraps the existing, well-tested secp256k1 Schnorr verification routine.

This commit is a routine code reorganization. It moves the TapTweak trait and its implementations from the main bitcoin crate into a smaller taproot-primitives crate. The actual logic for tweaking Taproot keys is copied unchanged; only its location in the codebase changes. There is no security bug being fixed or introduced.

This commit adds a missing 'ExactSizeEncoder' implementation for the WitnessEncoder in the rust-bitcoin library. Previously, WitnessEncoder only implemented the basic Encoder trait, even though the underlying encoders already supported exact-size reporting. The change uses an existing macro to automatically provide the exact-size capability and adds tests to verify the reported length matches the actual encoded bytes. There is no direct security vulnerability being fixed; it is a correctness and API-completeness improvement.

This commit only updates three text files that list the public API surface of the `bitcoin_hashes` crate. It records two newly added methods (`hash` and `with_input`) on the `HashEngine` trait. There are no code changes, no bug fixes, and no security-sensitive behavior introduced by this commit itself.

This commit adds a new convenience method called with_input to the hash engine API. It is purely a quality-of-life change that lets callers chain hash-input calls together. There is no security-relevant change: the existing input method still does the actual work, and no behavior, validation, or cryptographic logic is modified.

This commit is a routine performance and code-quality refactor. It replaces dynamically-dispatched formatter parameters with concrete Rust formatter types so the compiler can inline the code. There is no security-relevant change: no new inputs are accepted, no validation logic changes, and no sensitive data handling is altered.

This commit is a simple renaming of a dependency alias used only in fuzz testing code. It changes 'old_bitcoin' to 'bitcoin_0_32' throughout the fuzz test suite and generation script. There is no change to production code, no security fix, and no vulnerability introduced.

This commit only adds and reorganizes fuzz testing code. It brings older 0.32.x fuzz targets onto the master branch and switches them from hongfuzz to libfuzzer. There are no changes to production library code, so ordinary users of the crate are not affected and no new security vulnerability is introduced.

This is a small build-configuration cleanup, not a security fix. The change makes the 'alloc' feature automatically enabled whenever the 'serde' feature is enabled, because serializing to non-human-readable formats requires allocating memory. It also removes an unnecessary 'hex' feature gate from the serde module. There is no vulnerability here.

This commit only edits changelog Markdown files. It documents that several prior releases were yanked from crates.io because their required Rust version was raised too aggressively, and it adds notes about newer replacement releases. There are no code changes, no bug fixes, and no security patches in the diff.

This is a one-word documentation fix in a Rust macro. The generated documentation for a cryptographic tag structure was accidentally referring to a non-existent variable name, so it displayed broken placeholder text like '[`$hash_name`]' instead of the actual tag name. The change makes the docs show the correct tag name. There is no code behavior change and no security impact.

This commit only adds new unit tests to verify that a previously changed function, Target::from_compact, returns zero when a Bitcoin 'compact' difficulty value overflows a 256-bit target. It does not change any production code. The tests confirm the overflow behavior and check values right at the overflow boundary.

This commit fixes a bug in how rust-bitcoin converts Bitcoin 'compact' difficulty targets into full numeric Target values. Previously, if the compact value encoded a number too large to fit in a valid Target, the code would silently produce a truncated/wrapped result instead of treating it as invalid. The fix makes overflow behave like an invalid negative mantissa: return zero. This aligns the library with Bitcoin Core's consensus behavior, reducing the risk of consensus divergence or incorrect difficulty calculations.

This commit adds a small convenience method that lets any hash type compute a hash from a chunk of data in a single call. It is a pure API addition with no changes to existing behavior, no bug fixes, and no security-related content.

This commit fixes a bug in how the library counts 'signature operations' (sigops) in Bitcoin scripts. A small cache that remembers recently pushed numbers was not being cleared after signature-checking opcodes. This could cause a later multi-signature operation to incorrectly reuse a stale number, making the sigop count too low or too high in edge cases. The fix resets the cache whenever a signature opcode is seen, matching Bitcoin Core's consensus behavior.