rust-bitcoin

This commit only updates a public API listing file (all-features.txt) to reflect that several decoder types now expose a new public method called min_bytes_needed(). It is a documentation/tracking change with no actual code modifications, no security fixes, and no behavior changes.

This commit adds a new way to decode Bitcoin data directly from a stream or file reader, plus a small required method on all decoders that reports how many more bytes are needed. It is a feature addition, not a fix for a known security bug. There is no evidence in the commit or supplied references that it addresses a vulnerability.

This commit fixes a one-word typo in a Rust source code comment. The comment for a PSBT (Partially Signed Bitcoin Transaction) output map constant incorrectly referenced 'PSBT_IN_PROPRIETARY' (input) instead of 'PSBT_OUT_PROPRIETARY' (output). No executable code was changed, so there is no security or functional impact.

This commit corrects a typo in a code comment. The actual numeric constant was already correct (0x15); only the comment above it wrongly said 0x14. There is no functional code change and therefore no security impact.

This commit adds new helper functions for reading and decoding Bitcoin consensus data from byte slices and buffered I/O readers. It is a routine feature addition with no apparent security bug. The code includes proper error handling and unit tests.

This commit is purely a code-formatting run by the rustfmt tool. It only reorders imports, breaks long lines, and adjusts whitespace. There are no functional changes, no bug fixes, and no security-related alterations.

This commit only adds compiler hints (#[inline]) to small functions that simply pass work along to other functions. It does not change what the code does, only how the compiler may optimize it. There is no security relevance.

This commit only updates a generated text file that lists the public API surface of the crate. It records that a new type, AmountDecoder, is now exposed, but it does not change any actual source code, logic, or behavior. There is nothing here that could introduce a security vulnerability.

This commit is a routine API snapshot update. It only changes a generated text file that lists public API signatures, reflecting that some Encoder trait implementations no longer take a lifetime parameter. No actual source code, logic, or security behavior changed.

This commit only updates a generated text file that lists the public API surface of the `bitcoin_units` crate. It adds and removes entries reflecting other code changes (new decoder error types, new `Default`/`new` functions, changed error type aliases), but contains no actual source code changes. There is nothing in the commit that fixes, introduces, or alters program behavior, so it has no security relevance on its own.

This commit is a defensive API-hardening change, not a fix for an active security bug. It hides the internal details of an error type used when decoding Bitcoin amounts, so future library changes cannot accidentally expose or depend on those internals. It does not change how amounts are actually decoded or validated.

This commit adds public constructors and Default implementations for several data decoder types in the rust-bitcoin 'units' crate. It is a straightforward API usability improvement for downstream users and does not change any decoding logic, parsing rules, or security behavior.

This commit only updates a generated public-API listing file (api/units/all-features.txt). It records that new decoder types and traits for consensus encoding are now part of the exposed API, but it does not contain any actual code changes, bug fixes, or security patches. There is nothing here that directly creates or fixes a vulnerability.

This commit adds decoding logic for several Bitcoin unit types (amounts, block heights, lock times, sequence numbers, block times) so they can be read from a byte stream, mirroring existing encoding logic. It is a routine feature addition, not a security fix.

This commit is a simple rename of an error type from 'UnexpectedEof' to 'UnexpectedEofError' to follow the project's naming policy. It only moves the type definition to the bottom of the file and updates all references. There is no functional change and no security impact.

This commit only fixes a typo in documentation comments. The word 'Encodes' was changed to 'Decodes' in two Rust source files to accurately describe what the function does. No code behavior was changed.

This commit is a routine refactoring of benchmark code. It moves ChaCha20 performance tests out of the source crate and into a separate Criterion-based benchmark suite. There is no change to the actual ChaCha20/Poly1305 library code, no bug fix, and no security-related change.

This commit fixes a single typo in a code comment ('pre-pended' to 'prepended'). No executable code, logic, or data handling was changed. It has no security relevance.

This commit fixes a single spelling mistake in a documentation comment ('consenus-encoding' to 'consensus-encoding'). It changes no code, no build files, and no executable logic. There is no security relevance.

This commit only adds and reorganizes fuzz testing code. Fuzz tests are automated quality-assurance tools that feed random or structured data to library functions to look for crashes or incorrect behavior. No changes are made to the actual Bitcoin library code that applications would use, so this commit cannot introduce a security vulnerability in shipped software on its own.

This commit is a routine internal refactoring of how composite data decoders combine error types. It removes a custom Either sum type and instead uses Rust's standard trait conversion (From) plus phantom data to enforce that all inner decoder errors can be converted into a single common error type. There is no indication this fixes a security bug; it is a design/API cleanup.

This commit fixes a single typo in a comment ('used' to 'use'). No code behavior changes, and there is no security relevance.

This commit is a routine refactoring of benchmark tests. It moves performance-measuring code out of the main bitcoin crate into a separate 'benches' crate and switches the benchmarking framework from Rust's built-in nightly-only 'test' harness to the popular 'Criterion' library. No application logic, security checks, or public APIs are changed.

This commit adds new building blocks for combining multiple data decoders in sequence inside the rust-bitcoin library. It is a pure feature addition: it introduces helper types (Decoder2, Decoder3, Decoder4, Decoder6 and an Either error type) that let developers chain decoders together, plus tests showing they work. There is no bug fix, no mention of any security issue, and nothing in the code appears to create a vulnerability.

This commit adds a new helper decoder called ArrayDecoder to the rust-bitcoin consensus_encoding crate. It simply reads a fixed number of bytes from a stream and returns them as an array. There is no bug fix, behavior change, or security-sensitive modification here—just new code and tests.