rust-bitcoin

This commit only fixes spelling mistakes in comments and documentation strings. No code behavior was changed, so it has no security impact.

This commit only fixes typos in code comments by adding a missing space inside 11 files. No program logic, security settings, or behavior changed.

This commit only fixes documentation comments for two deprecated Rust functions. It does not change any executable code, so it cannot affect program behavior or security.

This is a small internal code cleanup in a Rust Bitcoin library. It removes an unused 'Transitioning' state from a two-stage data decoder and simplifies how the decoder switches from its first stage to its second stage. There is no indication this fixes a security vulnerability or changes observable behavior for users.

This commit is a simple internal rename and documentation cleanup. It renames a temporary error state inside a Bitcoin transaction decoder from 'Transitioning' to 'Errored' and updates the panic messages to be clearer. It also removes one panic that shouldn't have been there and replaces it with a safe dummy value. There are no observable behavior changes for users.

This commit fixes a panic (sudden crash) in the Rust Bitcoin library's transaction decoder. Previously, if a caller tried to finish decoding a Bitcoin transaction before all its data had been received, the program would crash with a panic. Now it returns a normal error instead, which is safer and easier for applications to handle gracefully.

This commit only adds a new unit test that checks how the library handles incomplete Bitcoin transaction data. It does not change any production code, fix a bug, or introduce a security feature. The test verifies that decoding truncated transaction bytes correctly produces an error rather than a valid transaction.

This commit is a code cleanup inside the Bitcoin transaction decoder. It removes helper functions that could panic if called in the wrong state and rewrites the decoder's main loop to avoid needing those helpers. The author explicitly states this is a refactor with no observable behavior changes, and the diff supports that reading: the same state machine, transitions, and error paths remain, just reorganized.

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.