rust-bitcoin

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 version bump for the internal 'bitcoin-internals' crate from 0.4.0 to 0.4.1, with matching updates to lock files and a dependent crate's dependency line. It contains no code changes, bug fixes, or security-related content.

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 removes extra spaces inside comments and a user-facing error message string. It does not change any executable code, logic, or behavior. There is no security relevance.

This commit adds version numbers to two internal Rust package dependencies in a Cargo.toml file so the crate can be published to a package registry. It is a routine build/publishing configuration change with no security relevance.

This commit replaces a named constant with the number 9 in one place. It is a straightforward code cleanup with no security relevance. The value 9 is the well-known maximum byte length of a Bitcoin compact-size integer encoding, and the change is functionally identical.

This commit is a routine release-preparation change. It bumps the version number of the `bitcoin-consensus-encoding` crate from 0.1.0 to 1.0.0-rc.0, updates two lock files, adds a changelog entry, and pins that version in two other internal crates that depend on it. There are no code changes and no security relevance in the diff itself.

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 is a tiny fix inside a fuzz test (automated random-input test) for the rust-bitcoin library. It changes the placeholder value used when computing a Bitcoin witness commitment from an empty byte slice to the correct 32-byte all-zero value required by the Bitcoin protocol (BIP-141). The change only affects test code, not the library that real users run, so it does not create a security vulnerability in the shipped software. It is a correctness improvement to make the fuzz test exercise the real code path more faithfully.

This commit only fixes a spelling mistake in the name of a test function ('exaustively' to 'exhaustively'). It does not change any executable code, behavior, or security properties of the project.

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 fixes two spelling/grammar mistakes in code comments and documentation strings within a Bitcoin signature hashing file. There are no code behavior changes, no bug fixes, and no security implications.

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 code cleanup in the rust-bitcoin library. It changes an encoding helper function so that it returns an empty byte slice instead of a special 'no value' (None) marker when there is nothing left to encode. The behavior of the code is intended to stay the same; only the way callers check for the end of data is simplified. There is no indication this fixes a security bug.

This commit only adds a new unit test to the rust-bitcoin consensus_encoding crate. It verifies that an encoder correctly handles empty byte slices when chained between non-empty slices. There is no code change to production logic, no bug fix, and no security relevance.

This commit fixes a single-word grammar typo in a Rust source code comment, changing 'decode' to 'decoded'. It does not alter any executable code, data structures, error handling, or cryptographic behavior.

This commit fixes a small but real integer-conversion bug when reading a witness data cursor on 16-bit platforms. Previously a 32-bit position value was silently truncated to 16 bits, which could make the code read the wrong memory offset or return an incorrect index. The fix validates the conversion and returns None if the value does not fit in a usize. On normal 32-bit and 64-bit systems the bug is not reachable because usize is already large enough.

This commit simply removes a one-line comment that had become outdated. The comment claimed a helper function was duplicated in another file, but that duplicate no longer exists. No actual code behavior was changed, so there is no security impact.

This commit adds a small safety check in the code that reads Bitcoin transaction witness data. Previously, the code directly converted a length value from a u64 to a usize, which on very small systems (16-bit) could silently truncate a large number into a small one, potentially causing incorrect data reads. The new helper function rejects impossibly large lengths and safely checks whether the value fits in a usize. It is a defensive hardening change, not a fix for a confirmed exploitable bug.

This commit fixes a typo in a fuzz-testing shell script and removes an unused helper function. It only affects internal testing tooling, not the library code that users rely on. There is no security impact on the Rust Bitcoin library 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 is a trivial documentation-only change in an example file. It updates two comments to reflect the correct module path for a wrapper type (`bitcoin_io::FromStd` instead of `bitcoin_io::bridge::FromStd`). No executable code was changed, and there is no security relevance.

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.