rust-bitcoin

This commit only adds a documentation comment to the Target type explaining that it does not enforce a maximum value limit. No code behavior was changed, and no security vulnerability is present in the commit itself.

This commit only updates generated API snapshot files that document the public interface of the Rust Bitcoin crates. It does not change any source code, logic, or behavior. The snapshots reflect a separate, earlier code change that added lifetime parameters to encoder types. There is no security issue in this commit itself.

This commit is a purely cosmetic renaming of lifetime parameters in Rust code. It changes labels like 's, 'a, and 'e to consistently use 'e across encoder-related code. There is no functional change, no bug fix, and no security impact.

This commit is a Rust type-system cleanup. It changes a macro that creates encoder wrapper types so that every wrapper must carry a lifetime parameter, and updates all uses across the codebase. There is no change to runtime behavior, wire format, or cryptographic logic. It prevents future misuse of the macro but does not fix a known exploitable bug.

This commit is a minor internal code cleanup in the Rust Bitcoin library. It replaces a long, complex type definition inside a macro with a shorter type alias name. There is no change to how transactions are encoded, no change to public behavior, and no security relevance.

This commit is a routine internal code reorganization in the rust-bitcoin library. It moves several key-related wrapper types into a single private 'encapsulate' module and re-exports them, without changing their public behavior or adding any security fixes. There is no indication of a vulnerability being patched.

This commit is a routine code cleanup. It adds a new public constructor method called from_secp for the Keypair type and makes the existing From conversion use that constructor. It also moves an existing inner accessor method to a different spot in the file. There is no security fix or behavior change.

This commit is a code cleanup in the rust-bitcoin library. It replaces direct internal access to cryptographic key data (like reading the hidden `.0` field) with official getter methods and constructors. There is no direct evidence this fixes an active security bug, but it strengthens encapsulation so future mistakes are less likely.

This commit is a routine API cleanup: it renames a method from `into_inner()` to `to_inner()` on a public-key wrapper type and keeps the old name as a deprecated alias. There is no security bug, no behavior change, and no vulnerability introduced or fixed.

This commit is a routine API cleanup, not a security fix. It hides the internal secp256k1 public key inside the CompressedPublicKey type and replaces direct field access with a constructor (from_secp) and a getter (to_inner). That improves encapsulation but does not change how keys are validated or used. There is no evidence this fixes a vulnerability.

This commit fixes a minor display bug in how certain Bitcoin hash values are printed as debug text when the optional 'hex' feature is turned off. Reversed hash types (like transaction IDs in Bitcoin, which are conventionally shown backwards) were being printed in the wrong order. This only affects debug/log output, not the actual hash data or cryptographic operations, so it is not a direct security vulnerability.

This is a small, safe API refactor. A helper function that writes bytes as hexadecimal text was changed to accept any iterator over bytes instead of only a fixed slice. This does not fix a vulnerability and does not change runtime behavior for existing callers.

This commit adds extra text formatting abilities (like showing numbers in hexadecimal, binary, or octal) to three simple numeric wrapper types in the rust-bitcoin library: block version, transaction version, and compact target. It is a routine usability improvement with no security relevance.

This commit only adds two automated formal-verification test cases (Kani proofs) that check Bitcoin's variable-length integer encoding round-trips correctly. It does not change any production code, fix a bug, or introduce a security-relevant behavior change. There is no indication of a vulnerability or security patch.

This commit is an automated code-formatting run by rustfmt. It only changes whitespace, line breaks, import order, and other stylistic details across 18 files. No program logic, security behavior, or functionality was altered.

This commit only changes test code. It expands existing unit tests for the AddrV2 network address type so that deserialization is checked with both the old `deserialize` helper and a newer `encoding::decode_from_slice` function. No production code was modified, so it cannot directly introduce a runtime security vulnerability.

This commit adds the ability to decode (read/parse) a newer Bitcoin peer-address format called AddrV2. Before this change, the code could encode (write) these addresses but apparently could not decode them. The new decoder checks that address lengths match what each network type expects, rejects some invalid address encodings (like wrapping an old Tor or IPv4 address inside IPv6), and reports errors cleanly. It is a normal feature-completion patch, but because it handles untrusted network input, any mistakes here could create parsing bugs.

This commit only updates a test file. It refactors an existing unit test for the `AddrV2` network address type so that expected byte sequences are stored in variables and also compared against a second serialization helper (`encoding::encode_to_vec`). There is no change to production code, no bug fix, and no security-related behavior change.

This commit adds a new way to serialize Bitcoin peer-to-peer address objects (AddrV2) using a state-machine style encoder. It is a feature/refactoring change that introduces a new code path for encoding addresses, but does not by itself fix a known security bug or introduce an obvious vulnerability. The new encoder mirrors the existing consensus_encode logic, so the main risk is a subtle implementation bug in the new encoder that could cause incorrect serialization or a panic.

This commit only updates automatically-generated API snapshot files to reflect a new MuHash type that was added in a previous code change. No actual source code is modified, and there is no security fix or vulnerability here.

This commit adds a new public type called MuHash to the rust-bitcoin hashes library. It is purely a wrapper around a 384-byte byte array so that downstream projects can label muhash3072 digests with a meaningful Rust type. The commit does not implement the hash algorithm itself, change any existing behavior, or fix any bug. There is no security-relevant change.

This commit simply bumps the version number of a third-party CI linting tool (cargo-semver-checks) used in GitHub Actions from 0.45.0 to 0.46.0. It changes one line in a workflow configuration file and has no effect on the actual Bitcoin library code, its APIs, or its runtime security.

This commit fixes a panic (sudden crash) in a Bitcoin transaction-signing helper. The function `spend_utxo` previously assumed that a referenced transaction output always existed, and used unchecked array indexing. If the output was missing, the program would crash instead of returning a proper error. The fix replaces the unchecked lookup with a bounds-checked one that returns a clean error.

This commit only adds a new unit test that checks whether an error message is non-empty and, when the standard library is available, whether the error has an underlying cause. It does not change any production code, fix a bug, or alter behavior. There is no security relevance.

This commit only adds new unit tests for the ScriptBuf type. It does not change any production code, fix bugs, or alter behavior. There is no security relevance.