rust-bitcoin

This commit only adds a new automated test. It does not change any production code, fix a bug, or alter behavior. The test checks that when a Bitcoin address has an invalid payload length, the error message reports the actual decoded payload size (22 bytes) rather than the length of the base58-encoded string. There is no security issue in this change itself.

This is a minor code cleanup in a benchmark file. A Rust linting tool (Clippy) complained that the benchmark was passing a meaningless empty value to a function. The developer changed the code to silence the lint. It does not affect real users, security behavior, or runtime code.

This commit only cleans up Rust code style by replacing explicit lifetime names with a shorthand. It does not change what the code does, how it handles data, or any security behavior. There is no security issue here.

This is a small internal code cleanup in a Rust Bitcoin library. It removes a redundant boolean flag and instead uses the presence or absence of an optional decoder object to track the same state. The commit message and diff show no change in behavior, input handling, or output results.

This commit simply removes a convenience function (`with_length_prefix`) from an internal byte-slice encoder in a work-in-progress Rust Bitcoin consensus-encoding module. Users are told to compose an explicit length-prefix encoder manually instead. There is no bug fix, no security patch, and no indication this change addresses any vulnerability.

This is a small internal code cleanup in the rust-bitcoin library. It changes how a Bitcoin script's byte length is recorded during serialization, making the length prefix explicit rather than hidden inside another helper. There is no indication this fixes a security bug; it appears to be a refactoring step before removing an old helper constructor.

This commit only changes a code comment to make it clearer which Bitcoin script opcodes are treated as data pushes versus regular opcodes. No actual code behavior was changed, so there is no security impact.

This commit removes an unnecessary internal re-export of a small helper macro. It is a code cleanup found by the Clippy linter and has no security relevance.

This commit fixes a typo in a documentation comment. The comment incorrectly referred to a different type (TxMerkleNode) when it should have referred to CompactTarget. There is no code behavior change and no security impact.

This commit only updates a mutation testing configuration file. It tells the mutation testing tool not to bother testing certain simple functions that are just type casts for performance reasons. There is no code change, no bug fix, and no security relevance.

This commit only updates a mutation-testing configuration file. It tells the automated mutation-testing tool not to alter two specific functions because those alterations would make tests run forever. It does not change any actual Bitcoin library code, fix a runtime bug, or address a security vulnerability.

This commit only changes a configuration file for mutation testing. It makes an existing test exclusion more specific so that future code additions are still tested. There is no change to the actual Bitcoin library code, no bug fix, and no security relevance.

This commit fixes a minor error-message bug. When a Bitcoin base58 address decoded to the wrong number of bytes, the error reported the length of the original string instead of the length of the decoded payload. The actual validation logic did not change; only the diagnostic detail is corrected.

This commit adds a new way to serialize Bitcoin blocks into bytes in the rust-bitcoin library. It is a routine feature addition that wires together existing serialization code for block headers and transactions. There is no indication of a security bug or fix.

This commit is a straightforward internal code cleanup. It replaces a custom hand-written encoding helper for Bitcoin transaction witness data with a reusable, already-existing encoder component. There is no indication of a bug fix or security change.

This commit simply makes a previously internal helper type called CompactSizeEncoder available for public use. It is a one-line export change with no functional code modifications, no bug fixes, and no security implications visible in the diff.

This commit adds a new helper for writing Bitcoin-style compact-size numbers. It is a straightforward feature addition with no visible security bug. There is no indication it fixes a vulnerability or introduces a dangerous behavior.

This commit removes one obsolete Clippy lint rule from a project configuration file. Clippy is a Rust code-quality tool, not part of the actual Bitcoin library code. The change has no effect on program behavior, network handling, cryptography, or user data, and therefore has no security relevance.

This commit is a routine documentation and build-helper update. It adds a newly created Rust package (`bitcoin-consensus-encoding`) to the dependency tree generator script (`justfile`) and regenerates the `docs/dep-tree` file so the published diagram matches the project's actual crates. There is no code change, no bug fix, and no security relevance.

This commit is a routine code cleanup. It adds a `new()` constructor to a small helper type called `CompactSizeDecoder` and makes the existing `Default` implementation use that constructor. It does not change behavior, fix a bug, or address any security issue.

This is an automated code-formatting commit from rustfmt. It only changes whitespace and line breaks in two Rust source files. There is no functional change, no bug fix, and no security relevance.

This commit fixes a single grammar mistake in a documentation comment, changing 'it's' (with apostrophe, meaning 'it is') to 'its' (possessive). It does not change any executable code, behavior, or security properties.

This commit fixes a single typo in a documentation comment, changing 'available on at' to 'available at'. There is no code change and no security relevance.

This commit fixes a stray extra quotation mark in a documentation comment. It is a typo correction with no effect on program behavior or security.

This commit is a minor code-style cleanup in a Rust Bitcoin library. It changes one line in a verification test file, replacing a wildcard import ('use super::*') with two specific imports ('use super::{Amount, SignedAmount}'). There is no functional change to the library, no bug fix, and no security relevance.