rust-bitcoin

This commit is a simple rename of an error type from 'UnexpectedEof' to 'UnexpectedEofError' to follow the project's naming policy. It only moves the type definition to the bottom of the file and updates all references. There is no functional change and no security impact.

This commit only fixes a typo in documentation comments. The word 'Encodes' was changed to 'Decodes' in two Rust source files to accurately describe what the function does. No code behavior was changed.

This commit is an automated code-formatting run by rustfmt. It only changes whitespace, line breaks, import ordering, and other stylistic details. No program logic, security checks, or behavior were altered.

This commit is a minor code cleanup in a Rust Bitcoin library. It removes an unnecessary intermediate variable when encoding very large numbers in a compact size format. There is no functional change and no security impact.

This commit simply updates the version of the Rust nightly compiler used by the project's automated GitHub CI testing from one weekly snapshot to the next. It changes one line in a configuration file and has no direct security relevance to the library code or its users.

This commit is a routine refactoring of benchmark code. It moves ChaCha20 performance tests out of the source crate and into a separate Criterion-based benchmark suite. There is no change to the actual ChaCha20/Poly1305 library code, no bug fix, and no security-related change.

This commit only adds a new README.md file inside the benches folder. It is pure documentation explaining how to run and add benchmarks. No program code was changed, so it cannot introduce a security vulnerability or fix one.

This commit is a routine refactoring that moves hash benchmarking code from inside the main source files into a separate benchmark suite using the Criterion library. It does not change how the hashing functions work, what data they process, or how they are exposed to users. There is no security fix or vulnerability here.

This commit fixes a single typo in a code comment ('pre-pended' to 'prepended'). No executable code, logic, or data handling was changed. It has no security relevance.

This commit fixes a single spelling mistake in a documentation comment ('consenus-encoding' to 'consensus-encoding'). It changes no code, no build files, and no executable logic. There is no security relevance.

This commit only adds and reorganizes fuzz testing code. Fuzz tests are automated quality-assurance tools that feed random or structured data to library functions to look for crashes or incorrect behavior. No changes are made to the actual Bitcoin library code that applications would use, so this commit cannot introduce a security vulnerability in shipped software on its own.

This commit simply updates a GitHub Actions workflow file to use a newer stable version of the Rust compiler (1.90.0 instead of 1.89.0). It is a routine CI maintenance change with no security relevance.

This commit only adds a new test file that exercises existing encoding wrapper types. It does not change any production code, fix bugs, or alter behavior. There is no security relevance.

This commit is a routine internal refactoring of how composite data decoders combine error types. It removes a custom Either sum type and instead uses Rust's standard trait conversion (From) plus phantom data to enforce that all inner decoder errors can be converted into a single common error type. There is no indication this fixes a security bug; it is a design/API cleanup.

This commit fixes a single-word typo in a documentation comment. It changes 'is case of overflow' to 'in case of overflow' in a code comment describing a checked addition function. There is no code behavior change and no security relevance.

This commit fixes a single typo in a comment ('used' to 'use'). No code behavior changes, and there is no security relevance.

This commit fixes a single-word typo in a comment inside a test file. It changes 'than' to 'that' in a comment describing a sanity check. There is no code, logic, or security change.

This commit fixes a single spelling mistake in a code comment, changing 'These form are' to 'These forms are'. It does not change any executable code, data structures, or behavior of the library.

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 is a routine code-quality change. It replaces the word `static` with `const` for a handful of Bitcoin script opcode aliases (like OP_TRUE and OP_FALSE). In Rust, `const` values are inlined at compile time and do not need a fixed memory address, which is perfectly safe here. There is no security-relevant change.

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 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.