rust-bitcoin

This commit adds a safety check in the Rust Bitcoin library's transaction decoder. It ensures that any transaction with more than one input cannot contain a 'coinbase-style' empty previous transaction reference. Such a reference is only allowed in the special coinbase transaction that creates new coins. Without this check, a malformed or malicious transaction could slip through and potentially cause incorrect behavior in software using this library to parse Bitcoin transactions.

This is an automated code-formatting commit. It only changes whitespace, line breaks, import order, and minor punctuation to match the latest rustfmt style. No program logic, APIs, or security behavior changed.

This is a minor internal code cleanup in the test suite only. It changes which internal Rust module provides certain Bitcoin data types used in tests, with no functional change to the library or any user-facing behavior.

This commit fixes a bug in a Bitcoin data decoder. Previously, if you stopped decoding early—before the full length prefix was read—the decoder would incorrectly report success with an empty result instead of reporting an error. The fix makes the decoder correctly return an 'unexpected end of data' error in those cases. This could matter for anyone parsing Bitcoin protocol data from partial or truncated inputs.

This commit only adds a new performance benchmark. It does not change any library code, fix any bug, or alter behavior. The benchmark measures how fast different methods can detect duplicate transaction inputs in a worst-case scenario. There is no security issue in the commit itself.

This commit fixes a single-word typo in a documentation comment. The word 'pre-tweaked' was changed to 'tweaked' to accurately describe the function's parameter. There is no code change and no security impact.

This commit is a routine version bump from 0.33.0-beta.0 to 0.33.0-beta.1 for the rust-bitcoin library. It only changes version numbers in package metadata and lock files, plus reorders a changelog list. There is no code change and no security relevance.

This commit is a routine version bump for a small Rust library called base58ck. It updates version numbers in package files, refreshes lock files, and adds a changelog entry. There are no code changes that fix or introduce any security issue.

This commit is a routine version bump for the bitcoin-primitives crate from 1.0.0-rc.1 to 1.0.0-rc.2, triggered by a new major release of an internal dependency. It updates version numbers in package manifests and lock files, and adjusts one test to import newly available type names. There is no security-relevant code change.

This commit is a routine version bump for a Rust library package called bitcoin-consensus-encoding, moving it from release candidate 2 to release candidate 3. It only updates version numbers in package metadata and lock files. There are no code changes, bug fixes, or security-related modifications visible in the diff.

This commit is a routine version bump for the bitcoin-units crate from 1.0.0-rc.3 to 1.0.0-rc.4, triggered by a major release of an internal dependency. It only changes version numbers in package manifests and lock files. There is no code change, no bug fix, and no security relevance.

This commit is a routine version bump for the internal 'bitcoin-internals' Rust package from 0.4.2 to 0.5.0. It updates version numbers in package manifests, lock files, and adds a changelog entry describing two minor internal code cleanups. There is no indication of any security fix or vulnerability being addressed.

This commit is a routine version bump for the bitcoin_hashes crate from 0.18.0 to 0.19.0. It updates version numbers in package manifests and lock files, and adds a changelog entry explaining the release was only needed because an internal dependency (bitcoin-internals) was upgraded. There are no code changes and no security relevance.

This commit only adds a changelog file documenting that a previous minor release (internals v0.4.1) accidentally included breaking changes and will be yanked. It changes no source code, build scripts, or runtime behavior. There is no security vulnerability here—just a documentation note about a semver policy mistake.

This commit is a simple internal code reorganization: it moves a helper function that decodes Bitcoin's compact-size integers from a shared 'internals' module into the only place that actually uses it, the witness handling code. The function's behavior, including its safety checks and panic conditions, is copied unchanged. There is no indication this fixes or introduces a security bug.

This commit is a routine internal code cleanup. It moves the logic for encoding Bitcoin 'compact size' numbers from one internal helper module into a dedicated encoder type, then updates call sites to use the new location. There is no security fix or behavior change intended.

This commit only adds a new unit test for an existing function (Witness::size). It does not change any production code, fix any bug, or alter behavior. There is no security relevance.

This commit is an automated code-formatting run by rustfmt. It only changes whitespace, line breaks, and the order of import statements. There are no functional changes, no bug fixes, and no security-related alterations.

This commit only adds public API snapshot files for the `hashes` crate and updates the script that checks for API changes. It does not modify any source code, behavior, or functionality. There is no security impact.

This commit only adds new automated tests for serializing and deserializing Bitcoin unit types (like fee rates, block heights, lock times, and sequence numbers). It does not change any production library code, so it cannot introduce a security vulnerability or fix one directly.

This commit only renames six test functions in a Rust test file to make their names more descriptive (adding 'amount' to clarify they test amount serialization). It changes no actual code behavior, no logic, and no public API. There is no security relevance.

This commit only renames three test-only struct fields from single-letter names (a, b, c) to descriptive names (block_height, block_height_interval, weight) inside a single Rust test file. It does not change any production code, logic, serialization format, or behavior. There is no security relevance.

This commit removes an unused import from a single Rust source file to silence a compiler warning. It does not change any behavior, logic, or security properties of the code.

This commit is a routine code-quality cleanup for the rust-bitcoin peer-to-peer (p2p) crate. It switches the crate from its own custom Clippy lint rules to the shared workspace lint rules, and makes the matching style fixes: reformatting numeric literals, adding backticks to documentation links, replacing manual loops with references, and changing a couple of function signatures to take references instead of owned values. There is no security fix here.

This commit is a routine code-quality cleanup for the internals subcrate. It switches the crate from its own custom lint rules to the workspace-wide lint rules, then fixes the style warnings that the stricter rules produced. There are no functional changes to how the library behaves, and no security fixes or vulnerabilities are introduced.