rust-bitcoin

This commit is a pure code reorganization: it moves existing implementations of string formatting, hex display, encoding, and decoding for Bitcoin transactions into a different order within the same file. No logic was changed, no bugs were fixed, and no security behavior was altered.

This commit only adds or removes blank lines between constant definitions in four source files to make the code style consistent. It does not change any program logic, values, or behavior, so it has no security relevance.

This commit removes old, deprecated function names and type aliases from the rust-bitcoin `units` crate in preparation for a 1.0.0 release. It is a routine API cleanup: no security bug is fixed and no new unsafe code is added. Downstream projects that still use the removed names will get compile-time errors and must switch to the replacement APIs.

This commit only updates generated API snapshot files (text listings of public functions) for the consensus_encoding crate. It adds entries for three new public functions that decode data using an explicit decoder type. There is no source code change, no bug fix, and no security relevance visible in the diff.

This commit adds new public helper functions to a Rust Bitcoin encoding library. The functions let callers decode data using a decoder type directly, rather than only through types that implement a specific trait. It is a pure API convenience addition and does not change existing behavior or fix any bug.

This commit only updates a generated text file that lists the public API surface of the crate. It adds entries for new public types and functions (a hex encoding/decoding error type and helper functions). There is no actual code change, no bug fix, and no security relevance visible in the diff.

This commit adds a new public helper function that lets users decode Bitcoin consensus data directly from a hexadecimal string, without needing to allocate a temporary byte vector. It is a pure feature addition: it introduces a new error type, exports the function under a feature flag, and includes unit tests. There is no indication in the commit that it fixes a security bug or that the change itself creates one.

This commit only renames a long crate name to a shorter alias inside test files. It does not change any real program code, behavior, or security properties. There is no security issue here.

This commit only updates documentation comments in a single Rust source file. It rewords explanations, adds a forward-compatibility note, and removes an embedded shell example from the docs. No code logic, function signatures, or behavior changed.

This commit fixes a bug in how the Bitcoin witness data decoder grows its internal buffer. Previously, when decoding witness data, the code could fail to reserve enough space before writing a size value, causing the program to panic and crash. The fix ensures the buffer is always expanded by at least a minimum amount when free space is low.

This commit adds a Rust compiler annotation to a helper function so that if it ever causes a program crash due to being full, the error message points at the code that called it rather than the helper itself. It does not change what the program does, only the quality of the crash diagnostic. There is no security vulnerability here.

This commit only fixes spelling and grammar mistakes in code comments and documentation. No program logic, code behavior, or security properties were changed.

This commit only reformats the import statements in a single test file. No code behavior, logic, or security properties changed.

This commit only changes how two existing tests are written. It replaces manual panic-catching code with Rust's standard #[should_panic] test attribute. The tests still verify the same behavior: that decoding functions panic when decoded values do not match expected values. There is no change to production code, no security fix, and no vulnerability introduced.

This commit only updates generated API snapshot text files in the rust-bitcoin hashes crate. It removes lines that list certain public type aliases and constants from the recorded public API surface. These files are used to detect unintended API changes during CI, not to implement behavior. There is no code change, no bug fix, and no security-relevant content in the diff.

This commit only updates three public API snapshot files to list two newly added test helper functions, `check_decode` and `check_decoder`. These are additions to the library's test/verification tooling, not changes to production code, and there is no indication of any security issue.

This commit only adds new helper functions for unit tests and refactors existing tests to use them. It does not change any production behavior, fix a bug, or alter security-relevant code paths. There is no indication this is a security patch.

This commit only updates two generated API snapshot files that list what functions and types are publicly exposed by the library. No actual source code was changed, and the commit message simply says 'Update API files.' There is no indication of a security fix or vulnerability.

This commit is purely a code-formatting cleanup. It re-indents lines, breaks long statements across multiple lines, and reorders imports to satisfy Rust style rules. No program logic, behavior, or security properties were changed.

This commit only updates documentation comments in a Rust Bitcoin encoding/decoding library. It rewrites explanations to match a recent API change where methods now return named enum values (like EncoderStatus::Finished) instead of plain true/false booleans. No actual code logic was changed, so there is no security impact.

This commit is a straightforward internal refactoring of the rust-bitcoin library's decoding machinery. It replaces a plain true/false return value from decoder methods with a new named DecoderStatus enum (NeedsMore / Ready). The change is purely about making the code easier to read and maintain; it does not alter what data is accepted, rejected, or how it is parsed. There is no indication this fixes a security bug or introduces a vulnerability.

This commit only updates generated API snapshot files (text listings of public functions/types). It adds two new public enum types, DecoderStatus and EncoderStatus, and changes the return type of several Decoder/Encoder methods from bool to those new enums. There is no source code change shown, no bug fix, and no security-relevant behavior described.

This commit is a routine code cleanup that fixes compiler lint warnings. It rewrites some pattern-matching to use shorter syntax, adds missing semicolons, converts a manual panic into an assertion, and reorganizes imports and test code behind feature flags. There is no functional change that affects security.

This commit is a straightforward code cleanup: it replaces a true/false return value from an encoder's 'advance' method with a clearly-named enum (HasMore/Finished). The behavior of the code is unchanged; it only becomes easier to read and maintain. There is no security fix or vulnerability here.

This commit only adds new unit tests and one test-tooling exclusion. It does not change any production code, so it cannot introduce or fix a security vulnerability on its own.