rust-bitcoin

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 is a small change to a developer helper script that checks whether the project's public API has changed. It makes the script temporarily use a known-good dependency lock file when run locally, then restores the developer's original lock file afterward. There is no security issue here.

This commit simply makes an existing type called AmountEncoder publicly available from a more convenient module path. It is a routine API usability change with no security implications.

This commit only updates a generated text file that lists the public API surface of the crate. It records that an existing type, `AmountEncoder`, was moved or renamed within the `bitcoin_units::amount` module. No actual source code, logic, or behavior changed, and there is no security relevance in this file update.

This commit adds a single missing semicolon in a Rust formatting function. It is a cosmetic/style fix to silence a Clippy lint and does not change program behavior or fix any security issue.

This is a tiny build-hygiene patch. A Rust compiler lint (Clippy) was warning that a constant named REVERSE was unused in some build configurations, so the developer added a feature gate so it only exists when the 'hex' feature is enabled. There is no security issue here.

This commit is a routine code cleanup, not a security fix. It replaces a large, detailed Bitcoin opcode module with a much smaller 'skeleton' version that keeps only the four opcode constants and the formatting helper actually used by the rest of the crate. No behavior that affects script parsing, validation, or consensus is changed.

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 fixes two minor mistakes in a documentation file: a missing 'fn' keyword in a code example and a duplicated word ('do should not' → 'should not'). These are purely cosmetic documentation corrections with no effect on actual code behavior or security.

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 only changes the mutation-testing configuration file. It tells the mutation-testing tool to skip testing certain code patterns because the tool's generated fake failures would be meaningless, not because of any real bug or security issue. There is no change to the actual Bitcoin library code that users run.

This commit only fixes two broken Markdown link references in the project's CHANGELOG.md file. It removes extra spaces and stray characters from the link syntax so the links render correctly. There are no code changes and no security implications.

This commit only fixes grammar in three comment lines inside test files. It changes 'The point of these tests are' to 'The point of these tests is'. There is no code, logic, or security change.

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.

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 new unit tests for existing encoder composition code. It does not change any production logic, fix bugs, or alter behavior. There is no security issue here.

This commit only adds two new fuzz-testing targets (automated test programs that feed random data to library functions) for the rust-bitcoin project. It does not change any production code, fix a bug, or alter behavior visible to users. There is no security issue in the commit itself.