rust-bitcoin

This commit adds convenience features to the rust-bitcoin library so that Bitcoin transactions can be easily converted to and from hexadecimal strings. It does not fix a bug, change security behavior, or introduce any obvious vulnerability. It is a routine API enhancement.

This commit adds a missing validation rule to the library's Bitcoin transaction decoder: a coinbase transaction (the special first transaction in a block that creates new coins) must have an input script between 2 and 100 bytes long. Before this change, the library would accept shorter or longer coinbase scripts, which violates Bitcoin consensus rules and could let malformed transactions slip through. The fix rejects them with clear errors and includes tests for the boundary cases.

This commit only updates an automatically-generated API listing file. It records that a new test-helper trait implementation (for generating random 'relative::LockTime' values) is now part of the crate's public API surface. There is no code change, no bug fix, and no security-sensitive behavior introduced.

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 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 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 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 is a simple code reorganization: a small trait called TxIdentifier that was defined in the main bitcoin crate is moved into the p2p crate's BIP-152 module because that was its only real user. There is no security fix, behavior change, or vulnerability being patched. It is purely a refactoring/cleanup change.

This commit tightens how the library decodes Bitcoin 'compact size' length fields. Previously the decoder could return a 64-bit value, which callers then had to convert to a machine-usable size. Now the decoder itself returns a usize and enforces a configurable upper limit. This is a defensive hardening change: it reduces the chance that a maliciously large length value causes memory problems or integer-conversion bugs later on. It is not a fix for a known active exploit.

This commit removes a documentation-only Rust compiler feature flag (`doc_auto_cfg`) from the BIP-158 crate. It does not change any executable code, runtime behavior, or security-sensitive logic. The change only affects how documentation is generated on docs.rs and appears to be a cleanup because the feature was unstable or causing issues.

This change is a routine internal dependency cleanup. The developers moved some shared type definitions (like block and transaction identifiers) from a large crate called `bitcoin` into a smaller, more focused crate called `bitcoin-primitives`. This reduces duplicate dependencies for downstream projects but does not change what the code does or fix any security problem.

This commit only updates test code. It removes an 'ignore' marker from a test and corrects the expected byte output for pushing a single zero byte onto a Bitcoin script. There is no change to production code and no security issue.

This commit only adds new automated tests for an existing data type called BlockTime. It does not change any production code, fix bugs, or alter behavior. There is no security issue here.

This is a tiny test-only cleanup commit. It removes an unused trait import and replaces a helper constructor with direct struct field assignment in a unit test. There is no security relevance.

This commit removes a third-party dependency called `arrayvec` from the `bitcoin-primitives` crate and rewrites how a Bitcoin block header is printed as text. The old code built the text in a small fixed-size buffer from `arrayvec`; the new code streams the bytes directly through an internal formatting helper. There is no security fix here—this is a routine dependency-reduction refactor.

This commit replaces the custom code that reads Bitcoin transaction witness data with a shared decoding library. The change is described by the author as a temporary, slightly messy refactor to keep an older decoding helper working while a newer encoding crate takes over. There is no claim in the commit that this fixes a security bug, and the diff itself is mostly code removal and plumbing a new error variant. It could affect how malformed witness data is rejected, but no vulnerability is disclosed or demonstrated.

This commit only reorders two Rust attribute lines on test functions so that #[test] appears above #[cfg(...)]. It is a cosmetic/style change with no effect on what code runs or how it behaves. There is no security relevance.

This commit only edits the project's changelog file. It documents an upcoming beta release and lists previously merged changes, but it does not modify any source code, build scripts, tests, or configuration. There is no security-relevant code change to review.

This commit removes a helper function called all_targets_satisfied() from the peer-to-peer (p2p) message handling code. That function used to check whether every block header in a 'headers' message met its own proof-of-work target. The change is framed by the author as a design cleanup: p2p should only encode and decode network messages, while proof-of-work verification should be done by the caller or elsewhere. Removing the check does not by itself create a vulnerability, but any downstream code that relied on this function to validate headers before processing them will no longer get that protection automatically. Those callers must now add the check themselves or use a different validation path.

This commit creates a brand-new, empty placeholder crate named `bitcoin-bip158` inside the rust-bitcoin workspace. It adds no executable code, no network functionality, no cryptographic operations, and no changes to existing crates. It is purely a project-structure refactor in preparation for later moving BIP-158 filter code out of the main `bitcoin` crate.

This commit only fills in placeholder version numbers in deprecation warnings. It does not change any program behavior, fix any bug, or introduce any security issue. It is a routine documentation/metadata cleanup.

This commit is a routine version bump for an internal helper crate. It only changes version numbers in package files and a changelog entry. There is no code change, no bug fix, and no security issue visible in the diff.

This commit refactors how Bitcoin peer-to-peer address errors are reported. It replaces a generic input/output error type with a new, more specific error type for addresses that cannot be routed over normal internet connections (Tor, I2P, CJDNS). This is a routine API cleanup, not a fix for an active security vulnerability. The change is part of a larger effort to reduce internal package dependencies.

This commit is a routine code reorganization: it moves the BIP-152 compact block module from the main `bitcoin` crate into the `p2p` crate, where it is more logically located. It also replaces an auto-derived hex formatting trait with a manual implementation for one small type. There is no security fix or behavior change visible in the diff.

This commit refactors how Bitcoin Merkle roots are calculated so the code works even when the optional 'alloc' memory allocator feature is disabled. It replaces a growable vector with a fixed-size 15-slot array, which limits the no-alloc path to at most 32,767 transaction IDs. The change is a feature-portability improvement, not a security fix, and it explicitly returns None when the no-alloc limit is exceeded rather than overflowing or corrupting state.