rust-bitcoin

This commit only adds new helper scripts that run an automated code-quality tool (Clippy) on each crate with default features disabled. It does not change any library code, fix a bug, or alter behavior. There is no security issue here.

This is a minor code cleanup commit. It moves one import statement behind a feature gate so that the Rust compiler's clippy lint tool no longer warns about an unused import when the library is built with no default features. There is no functional or security change.

This commit only updates the version (commit hash) of an internal maintainer-tools repository used by the project's GitHub Actions CI workflow. It does not change any application code, cryptographic logic, network handling, or user-facing behavior. There is no indication of a security fix or vulnerability.

This commit fixes a single incorrect word in a documentation comment. The comment previously said the encoder was for one type (TxOut) when it actually encodes a different type (OutPoint). No code behavior changed, and there is no security impact.

This commit only updates two text patterns in a mutation-testing configuration file. The patterns tell the mutation-testing tool which functions to skip. The function names changed slightly because of a Rust syntax cleanup (lifetime elision), so the skip patterns had to be updated to keep working. No program code, cryptography, network handling, or user-facing behavior was changed.

This commit only rewords a comment in a configuration file used for mutation testing. No code behavior was changed, so there is no security impact.

This is an automated code-formatting commit from rustfmt. It only changes whitespace, line breaks, import order, and other stylistic details. There are no functional changes and no security implications.

This commit adds new code to read (decode) Bitcoin data formats such as block headers, transactions, transaction inputs/outputs, and witness data in the rust-bitcoin library. It is a large feature addition rather than a clear security fix. The new decoders include length-limit checks and reject obviously invalid formats, but because this is brand-new parsing code, any mistakes could become memory-safety or denial-of-service issues in downstream Bitcoin software. There is no evidence in the commit message or diff that the authors are fixing a known vulnerability.

This commit only rewords two documentation comments in the source code. It changes the phrase 'script public key (scriptPubKey)' to '`scriptPubKey` (locking script)' to match more common Bitcoin terminology. No code behavior changes, no API changes, and no security implications.

This commit is a trivial configuration-only rename. It updates a single line in the project's mutation-testing exclusion file so that the correct function name ('read_limit') is skipped by the cargo-mutants tool, replacing the old name ('min_bytes_needed'). It does not change any production code, cryptographic logic, network handling, or user-facing behavior.

This commit only fixes grammar in code comments and renames a test function that had a typo in its name. There are no code behavior changes, no security fixes, and no functional patches.

This commit only updates an automatically generated API text file. It renames recorded trait implementations from `consensus_encoding` to `bitcoin_consensus_encoding` to match a recent code change. No actual source code, logic, or security behavior was changed.

This commit simply renames an internal Rust package from `consensus-encoding` to `bitcoin-consensus-encoding` so the crate name matches the one published on crates.io. It updates lock files, package manifests, and internal `use` statements accordingly. There is no change to program logic, no bug fix, and no security relevance.

This commit fixes a bug in how the library calculates the Merkle root, a fingerprint used to summarize all transactions in a Bitcoin block. An old Bitcoin vulnerability (CVE 2012-2459) lets someone craft a block with duplicate transactions that produces the same fingerprint as a valid block, potentially tricking software into rejecting the real block. The patch makes the library refuse to compute the root whenever it sees the duplicate pattern, so the invalid block is simply rejected and no confusion can occur.

This commit only corrects spelling mistakes in code comments and documentation strings. No program logic, function behavior, or security-relevant code was changed.

This commit is a straightforward internal code cleanup in the rust-bitcoin library's encoding machinery. It removes the automatic length-prefix behavior from a helper called SliceEncoder and instead makes callers explicitly combine a compact-size length encoder with the slice encoder. The actual serialized Bitcoin bytes produced for blocks and transactions remain the same; only the way the code is structured changes. There is no indication this fixes a security bug.

This commit only adds a new unit test that demonstrates an old Bitcoin bug (CVE 2012-2459). The test deliberately duplicates the last transaction in a real historical block and checks that the forged block still passes validation. The commit message and an inline comment ('FIXME fixed in next commit') make clear the test is documenting a bug that will be patched later. No actual fix is included here, so this commit by itself does not change any production behavior or introduce a vulnerability.

This commit fixes a spelling mistake in two documentation files, changing 'sciptcode' to 'scriptcode'. It does not change any code, program behavior, or security properties.

This commit only updates a generated text file that lists the public API surface of the crate. It renames a handful of method entries from `min_bytes_needed` to `read_limit` in the API listing. There is no actual source code change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit is a simple rename of a Rust trait method from `min_bytes_needed` to `read_limit` across the codebase, along with an update to its documentation to clarify that it represents an upper bound on bytes that can be safely read. There are no logic changes, no bug fixes, and no security implications.

This is a minor code-quality change. A constant used only in tests that require the 'alloc' feature was not itself behind that feature gate, causing a compiler warning (Clippy lint) when building without that feature. The patch adds the missing feature gate so the constant is only compiled when needed. There is no security impact.

This commit is a routine code-quality fix. It adds Rust feature gates so that certain test-only structs and imports are only compiled when the 'alloc' feature is enabled, silencing a Clippy warning about structs that are never constructed. There is no security relevance.

This is a routine maintenance change to a fuzz-testing file. It removes two deprecated test helper functions from a list so that an automated daily fuzzing job stops failing. There is no change to production code, no user-facing behavior, and no security fix.

This commit is a routine internal cleanup. It replaces deprecated function names with their newer equivalents in two helper methods that calculate Bitcoin transaction weight. The actual math and behavior remain the same, and the old functions are still kept (just marked as deprecated). There is no security issue here.

This commit only adds documentation comments describing situations where certain functions could panic due to arithmetic overflow. No code behavior was changed, so this is a documentation-only update with no security impact.