rust-bitcoin

This commit simply renames an internal Rust package from `consensus-encoding` to `bitcoin-consensus-encoding` so the crate name matches the one published on crates.io. It updates lock files, package manifests, and internal `use` statements accordingly. There is no change to program logic, no bug fix, and no security relevance.

This commit is a straightforward internal code cleanup in the rust-bitcoin library's encoding machinery. It removes the automatic length-prefix behavior from a helper called SliceEncoder and instead makes callers explicitly combine a compact-size length encoder with the slice encoder. The actual serialized Bitcoin bytes produced for blocks and transactions remain the same; only the way the code is structured changes. There is no indication this fixes a security bug.

This commit only updates a generated text file that lists the public API surface of the crate. It renames a handful of method entries from `min_bytes_needed` to `read_limit` in the API listing. There is no actual source code change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit is a simple rename of a Rust trait method from `min_bytes_needed` to `read_limit` across the codebase, along with an update to its documentation to clarify that it represents an upper bound on bytes that can be safely read. There are no logic changes, no bug fixes, and no security implications.

This commit is a routine internal cleanup. It replaces deprecated function names with their newer equivalents in two helper methods that calculate Bitcoin transaction weight. The actual math and behavior remain the same, and the old functions are still kept (just marked as deprecated). There is no security issue here.

This commit only adds documentation comments describing situations where certain functions could panic due to arithmetic overflow. No code behavior was changed, so this is a documentation-only update with no security impact.

This commit only adds a new automated test. It does not change any production code, fix a bug, or alter behavior. The test checks that when a Bitcoin address has an invalid payload length, the error message reports the actual decoded payload size (22 bytes) rather than the length of the base58-encoded string. There is no security issue in this change itself.

This commit only cleans up Rust code style by replacing explicit lifetime names with a shorthand. It does not change what the code does, how it handles data, or any security behavior. There is no security issue here.

This is a small internal code cleanup in a Rust Bitcoin library. It removes a redundant boolean flag and instead uses the presence or absence of an optional decoder object to track the same state. The commit message and diff show no change in behavior, input handling, or output results.

This commit adds a new way to serialize Bitcoin blocks into bytes in the rust-bitcoin library. It is a routine feature addition that wires together existing serialization code for block headers and transactions. There is no indication of a security bug or fix.

This commit simply makes a previously internal helper type called CompactSizeEncoder available for public use. It is a one-line export change with no functional code modifications, no bug fixes, and no security implications visible in the diff.

This commit is a routine code cleanup. It adds a `new()` constructor to a small helper type called `CompactSizeDecoder` and makes the existing `Default` implementation use that constructor. It does not change behavior, fix a bug, or address any security issue.

This commit adds a new generic decoder in the rust-bitcoin library for reading lists of items from Bitcoin's wire format. It is a feature addition with tests, not a fix for a known bug or vulnerability. There is no indication in the commit message or diff that this addresses a security issue.

This commit adds a new decoder for reading length-prefixed byte vectors in the rust-bitcoin consensus encoding library. It includes a hard cap of 4,000,000 bytes to prevent attackers from tricking the decoder into allocating excessive memory. The change appears to be a routine feature addition with defensive limits already built in, not a fix for a known vulnerability.

This commit adds new serialization (encoding) helpers for Bitcoin transaction data types in the rust-bitcoin library. It is a feature/refactoring change that introduces an alternative way to convert transactions, inputs, outputs, and related types into bytes. There is no indication in the commit that it fixes a security bug, and the included tests pass. The main risk is that any new serialization code could contain subtle correctness bugs, but nothing in the diff points to an exploitable vulnerability.

This commit adds a new way to serialize Bitcoin witness data into bytes. It is a straightforward feature addition with no visible bug fixes, no mention of security issues, and no changes to existing behavior. There is no indication this commit addresses a vulnerability.

This commit fixes two spelling mistakes: changing 'leafs' to 'leaves' in a code comment and adding the word 'the' in a rustfmt.toml comment. There are no code behavior changes, no security fixes, and no functional modifications.

This commit adds a new decoder for Bitcoin's 'compact size' integer format in the rust-bitcoin library. It is a feature addition, not a fix for a known security bug. The code carefully checks for non-minimal encodings (a common source of parsing bugs in Bitcoin) and includes unit tests. There is no indication in the commit or supplied references that this resolves a disclosed vulnerability.

This commit is a minor code cleanup in the Rust Bitcoin library. It changes how some standard Rust types are imported so the code is shorter and easier to read. There is no functional change, no bug fix, and no security relevance.

This is a tiny test-only fix that changes which Rust feature gate guards an import inside unit tests. It has no effect on production code and no security relevance.

This commit simply removes two test cases that only printed debug output to the console. No production code, logic, or security behavior is changed. It is a routine cleanup with no security relevance.

This commit only runs a code formatter on two fuzz test files. It reorders import statements so they appear alphabetically. There are no functional code changes, no bug fixes, and no security relevance.

This commit removes a redundant error-message assertion from three internal fuzz-testing programs. The removed line only printed a nicer message when a deserialization failed; the very next line still checks that the round-trip result matches the original value. It does not change any production library code, user-facing APIs, or security behavior.

This commit fixes a fuzz test so that it checks serialization round-trip correctness before modifying the object, rather than after. The change is purely a test logic correction and does not affect production code or introduce any security issue.

This commit fixes four spelling mistakes where 'PSBT' was incorrectly written as 'PBST' in documentation comments and an error message string. It does not change any program logic, data handling, or security behavior.