rust-bitcoin

This commit simply updates a fuzz-testing helper library called honggfuzz from version 0.5.57 to 0.5.58. It only changes version numbers and lock-file checksums in files related to fuzz testing. There is no indication this fixes or introduces a security problem in the actual Bitcoin library code that users rely on.

This commit fixes two typos in comments/constant names within PSBT serialization code. One renames a local constant from PSBT_SERPARATOR to PSBT_SEPARATOR (the value 0xff is unchanged), and the other fixes a grammar error in a comment. Neither change alters program behavior.

This commit simply updates the version of the Rust nightly compiler used by the project's automated GitHub CI tests from one weekly release to the next. It changes one line in a configuration file and has no direct security relevance to the software itself.

This commit only adds new unit tests for a slice encoder in the consensus_encoding crate. It does not change any production code, fix any bug, or alter behavior. There is no security relevance.

This commit only changes unit tests for the consensus encoding module. It rewrites how tests exercise the byte and array encoders, switching from a helper that collects all output into a vector to direct assertions about each encoding step. There is no change to production code, no bug fix, and no security relevance.

This commit fixes a bug in a Rust Bitcoin library component that encodes lists of items for the Bitcoin network protocol. When the list was empty, the encoder could fail to consume its internal 'compact size' marker on the first step, breaking its promised behavior of eventually returning 'no more data.' This could cause callers that stream or chunk encoded data to loop forever or behave incorrectly when encoding an empty list.

This commit simply bumps the version number of a CI linting tool (cargo-semver-checks) used in GitHub Actions from 0.43.0 to 0.44.0. It changes one line in a configuration file and has no effect on the actual Bitcoin library code, runtime behavior, or security.

This commit fixes a grammatical typo in a documentation comment, changing 'Cannot not convert' to 'Cannot convert'. It does not change any executable code, behavior, or security properties.

This commit fixes two spelling/grammar mistakes in code comments ('its' to 'it's' and 'is' to 'if'). No program logic, behavior, or security properties are changed.

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 fixes a one-letter typo in a documentation comment. The comment incorrectly said 'P2WPSH' and now correctly says 'P2WSH' (Pay-to-Witness-Script-Hash), matching the function name it describes. There is no code change and no security impact.

This commit is a small internal cleanup in a Rust Bitcoin encoding helper. It removes an unused index counter and instead tracks progress by advancing a slice reference. There is no indication this fixes a security bug or changes observable behavior for users.

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 is a routine code cleanup in the Rust Bitcoin library. It removes an unnecessary naming requirement for lifetimes in the encoding machinery, making the macro more flexible and the code easier to maintain. There is no security issue here.

This commit only fixes two typos in test documentation comments, changing 'CMerkleBlock' to 'MerkleBlock'. It does not change any actual code, behavior, or security properties.

This commit fixes a single-letter spelling mistake in an error message string: 'deserializaton' is corrected to 'deserialization'. It does not change any program logic, parsing behavior, or security properties.

This is a tiny, routine Rust code change that makes one internal type (`AmountDecoder`) publicly visible from a slightly more convenient module path. It adds no new logic, changes no behavior, and fixes no bug. There is no security relevance.

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 is a routine code-quality refactor in the rust-bitcoin library. It changes several decoder error types from a shared generic error into separate, type-specific wrapper errors so that different decoders can be combined more easily. There is no security vulnerability being fixed here; it is purely an API design improvement.

This commit adds a new helper type called SliceEncoder to a Rust Bitcoin library. It is purely additive: it lets developers encode a list of items into Bitcoin's wire format. There is no bug fix, no change to existing behavior, and no security issue visible in the code.

This commit only adds new performance benchmark tests for the ChaCha20-Poly1305 encryption code. It does not change any production code, fix any bug, or alter any security behavior. There is no security issue here.

This commit is a documentation-only fix. It corrects a broken internal link anchor in the project's CONTRIBUTING.md file and adds a short note pointing readers to a separate policy document. There is no change to code, no security relevance, and no risk to users.