rust-bitcoin

This commit renames Bitcoin script opcode constants to shorter names (for example, OP_PUSHNUM_1 becomes OP_1) and keeps the old names as deprecated aliases. It also changes how these opcodes are serialized to JSON, so any software that exchanges opcode names with this library may need to update its expected strings. There is no direct security flaw in the code change itself, but it is a breaking API/serialization change that could surprise downstream users.

This commit is a simple renaming cleanup inside the rust-bitcoin library. It replaces older, longer opcode names like OP_PUSHNUM_1 with shorter names like OP_1 everywhere they appear. The actual numeric byte values and behavior of the Bitcoin opcodes stay exactly the same, so there is no security risk.

This commit fixes three English grammar typos in comments and user-facing error messages within the Partially Signed Bitcoin Transaction (PSBT) module. It changes 'an non-ECDSA' to 'a non-ECDSA' and 'an ripemd160' to 'a ripemd160'. There are no code logic changes.

This commit only updates a generated public-API listing file (api/units/all-features.txt). It records that new decoder types and traits for consensus encoding are now part of the exposed API, but it does not contain any actual code changes, bug fixes, or security patches. There is nothing here that directly creates or fixes a vulnerability.

This commit changes a single error message string in a test file from 'Error in first array: ...' to 'Composite error: ...'. It is purely a wording cleanup in test code and has no security relevance.

This commit adds decoding logic for several Bitcoin unit types (amounts, block heights, lock times, sequence numbers, block times) so they can be read from a byte stream, mirroring existing encoding logic. It is a routine feature addition, not a security fix.

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