rust-bitcoin

This change is purely a code organization cleanup. It moves a handful of Bitcoin script opcode aliases (like OP_0, OP_TRUE, OP_NOP2) from outside a module into the 'all' submodule so that a wildcard import picks them up. No behavior of the library changes, and there is no security fix or vulnerability here.

This commit updates the declared minimum supported Rust version (MSRV) for one sub-crate from 1.63.0 to 1.74.0 so it matches the rest of the workspace. It is a build-metadata correction with no code changes and no security impact.

This commit only cleans up Rust compiler/clippy warnings about lifetime syntax. It changes how lifetimes are written in two places but does not alter what the code actually does. There is no security issue here.

This commit simply updates a fuzz-testing helper library called honggfuzz from version 0.5.56 to 0.5.57 in the project's lock files and fuzz-testing configuration. It does not change any production Bitcoin code, wallet logic, or network handling. There is no indication this is a security fix.

This commit simply renames two fuzz test files from 'deserialize_address.rs' to 'parse_address.rs' and 'outpoint_string.rs' to 'parse_outpoint.rs'. The actual code inside the files is unchanged. It is a routine cleanup with no security relevance.

This commit only updates the project's mutation-testing configuration file. It tells the mutation-testing tool not to try altering certain serde visitor error-message methods, because those changes would not be meaningful to test. There is no code behavior change, no bug fix, and no security relevance.

This commit only updates the mutation-testing configuration file to skip testing two additional deprecated methods. It does not change any production code, cryptographic logic, network handling, or user-facing behavior. There is no security issue here.

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

This commit only rearranges existing test code and renames one test. No production code was changed, and no security issue is present.

This commit only changes a benchmark test so it runs longer. It does not touch any production code, so it has no security impact on users of the library.

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 is a routine Rust type-system relaxation. It changes three encoding helper functions so they can accept trait objects and other unsized types, not just fixed-size types. There is no bug fix, behavior change, or security patch here—only a flexibility improvement for callers.

This commit adds a new way to serialize (encode) Bitcoin scripts in the rust-bitcoin library. It is a routine feature addition: it lets Script<T> be encoded with a length prefix, matching Bitcoin's consensus format. There is no indication of a security bug, fix, or vulnerability.

This commit adds a new optional feature to a low-level byte-encoding helper in the rust-bitcoin library. It lets callers prepend a Bitcoin-style 'compact size' length prefix when encoding a byte slice. The change is purely additive, includes tests, and does not alter existing behavior of the 'without length prefix' constructor. There is no indication it fixes a security bug or introduces a vulnerability.

This commit simply changes the visibility of a constant named MAX_ENCODING_SIZE from internal-only to public. It does not alter any behavior, logic, or data handling. There is no security issue here.

This commit only adds new unit tests for an existing encoding helper. It does not change any production code, fix bugs, or introduce new behavior. There is no security relevance.

This is a small internal Rust macro cleanup. It removes an unnecessary generic lifetime parameter from a macro that wraps existing encoder types. There is no functional change to how data is encoded or decoded, and no security relevance is visible in the commit.

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.

This commit adds new Rust traits (interface definitions) for a streaming, push-based Bitcoin consensus decoder. It only introduces abstract code patterns—no actual decoding logic for real Bitcoin data types, no changes to existing behavior, and no bug fixes. There is nothing here that directly affects security.

This commit only changes the wording of code documentation comments (rustdoc) from imperative to third-person style (e.g., 'Parse' to 'Parses'). It also adds a project policy note about this documentation style. No executable code, logic, or behavior was modified, so it has no security impact.

This commit is a routine dependency version bump in a build configuration file. It changes the required version of an optional test/fuzzing helper library from '1.4' to '1.4.1' so that it matches another crate in the same workspace and resolves a Cargo lock-file conflict. There is no indication this fixes or introduces a security vulnerability.

This is a routine continuous-integration (CI) maintenance patch. It makes the automated API-checking job use a fixed dependency lockfile and the --locked flag so builds are reproducible. There is no change to the library code that users run, and no security issue is being fixed or introduced.

This is a routine automated update by Dependabot that bumps the GitHub Actions 'actions/checkout' dependency from version 4 to version 5 in the project's CI workflow file. There is no indication of a security fix or vulnerability in the commit itself.

This commit only changes test code inside the rust-bitcoin library. It swaps internal struct-literal construction of script hash types for public constructor methods. There is no change to production code, no security fix, and no behavior change.