rust-bitcoin

This commit is a minor code cleanup that removes unnecessary copy operations (clones) inside test code only. It does not change any production behavior and has no security relevance.

This commit only adds a new test that encodes a Bitcoin transaction and decodes it again to make sure the result matches the original. It does not change any production code, fix a bug, or introduce a security issue. The commit message mentions a 'mutant in push_bytes,' which is testing jargon for a surviving fake code change during mutation testing, not a real vulnerability.

This commit only adds a new test case. It does not change any production code. The test checks that decoding a SegWit-formatted transaction with no witness data correctly produces an error. There is no fix or behavior change in the actual decoder.

This commit only removes two short documentation comments from a Rust trait implementation. The actual code behavior is unchanged. There is no security relevance.

This is a routine internal code reorganization. A helper function that feeds encoded data into a hash calculation was moved from one Rust crate to another, and the dependency direction between those two crates was reversed. The actual logic of the function did not change, and there is no indication this fixes or introduces a security bug.

This is an automated code-formatting commit from rustfmt. It only changes whitespace, line breaks, and brace style in two source files. No program logic, behavior, or security properties were changed.

This commit only adds new unit tests for encoding and decoding routines in the rust-bitcoin consensus_encoding crate. It does not change any production code, fix bugs, or alter behavior. The tests cover corner cases such as zero-length arrays, empty slices, boundary values for compact-size integers, and state transitions in combined encoders/decoders.

This commit removes a Rust compiler feature flag called doc_auto_cfg from 11 library files. The feature was removed in recent nightly Rust compilers and was causing documentation builds to fail when publishing crates. It is purely a build/documentation compatibility fix with no effect on the actual Bitcoin code or its security.

This commit only adds new fuzz testing targets for the consensus_encoding crate. Fuzz testing is an automated quality-assurance technique that feeds random or crafted inputs to code to find crashes or unexpected behavior. The commit does not change any production library code, so it cannot by itself introduce a security vulnerability or fix one.

This commit is a routine release preparation: it bumps the version number of the `bitcoin-units` crate from 1.0.0-rc.0 to 1.0.0-rc.1, updates the two lock files, adds an explicit version requirement to the dependency declarations in three other crates, and moves a couple of changelog entries under the new release heading. There are no code changes, no bug fixes, and no security-relevant behavior changes in the diff.

This commit only rewords a code-comment in a configuration file. It changes 'TODO' to 'TODO: Consider enabling this lint.' There is no code change, no behavior change, and no security relevance.

This commit fixes two spelling mistakes in code comments ('coversion' to 'conversion'). No program logic, behavior, or security properties were changed.

This commit corrects a single-word typo in a documentation comment. The comment for the Decodable trait incorrectly said 'encoded' and now correctly says 'decoded'. No code behavior changes.

This commit only updates a generated text file that records the project's public API surface. It changes the documented return type of several encoder helper methods from 'optional byte slice' to 'byte slice'. No actual source code, logic, or behavior changed, so there is no security issue in this commit itself.

This commit is a routine internal refactoring of how composite decoders report errors in the rust-bitcoin library. It replaces a generic error-mapping scheme with fixed error types for decoders that combine 2, 3, 4, or 6 sub-decoders. There is no indication this fixes a security bug or changes how data is parsed; it only changes the shape of error values returned when parsing fails.

This commit only adds documentation comments explaining that certain size-calculation functions can panic if an arithmetic overflow occurs. It does not change any actual code behavior, fix a bug, or introduce new functionality. There is no security-relevant code change.

This commit only removes two lines of stale explanatory comment from transaction decoding code. No code behavior changes, no security relevance.

This commit only fixes spelling mistakes in comments and documentation strings. No code behavior was changed, so it has no security impact.

This is a small internal code cleanup in a Rust Bitcoin library. It removes an unused 'Transitioning' state from a two-stage data decoder and simplifies how the decoder switches from its first stage to its second stage. There is no indication this fixes a security vulnerability or changes observable behavior for users.

This commit fixes a panic (sudden crash) in the Rust Bitcoin library's transaction decoder. Previously, if a caller tried to finish decoding a Bitcoin transaction before all its data had been received, the program would crash with a panic. Now it returns a normal error instead, which is safer and easier for applications to handle gracefully.

This commit is a simple internal rename and documentation cleanup. It renames a temporary error state inside a Bitcoin transaction decoder from 'Transitioning' to 'Errored' and updates the panic messages to be clearer. It also removes one panic that shouldn't have been there and replaces it with a safe dummy value. There are no observable behavior changes for users.

This commit only adds a new unit test that checks how the library handles incomplete Bitcoin transaction data. It does not change any production code, fix a bug, or introduce a security feature. The test verifies that decoding truncated transaction bytes correctly produces an error rather than a valid transaction.

This commit is a code cleanup inside the Bitcoin transaction decoder. It removes helper functions that could panic if called in the wrong state and rewrites the decoder's main loop to avoid needing those helpers. The author explicitly states this is a refactor with no observable behavior changes, and the diff supports that reading: the same state machine, transitions, and error paths remain, just reorganized.

This commit fixes a single incorrect word in a documentation comment. The comment previously said the encoder was for one type (TxOut) when it actually encodes a different type (OutPoint). No code behavior changed, and there is no security impact.

This commit adds new code to read (decode) Bitcoin data formats such as block headers, transactions, transaction inputs/outputs, and witness data in the rust-bitcoin library. It is a large feature addition rather than a clear security fix. The new decoders include length-limit checks and reject obviously invalid formats, but because this is brand-new parsing code, any mistakes could become memory-safety or denial-of-service issues in downstream Bitcoin software. There is no evidence in the commit message or diff that the authors are fixing a known vulnerability.