rust-bitcoin

This commit only fixes three incorrect comments in a test function. The comments mistakenly referred to 'transaction' when the test actually exercises the block Header type. No code behavior changes.

This is a small internal code cleanup in the rust-bitcoin library. It removes a hand-written wrapper type called HeaderIter and instead uses a newer built-in trait (ExactSizeEncoder) to achieve the same result. There is no user-visible behavior change and no security relevance.

This commit is a routine feature addition to the Rust Bitcoin library. It introduces a new ExactSizeEncoder trait that lets callers ask fixed-size encoders how many bytes they will produce, and adds an ExactSizeIterator implementation for the byte iterator. There is no security fix or vulnerability here; it is purely an API enhancement with tests.

This commit adds a safety check in the rust-bitcoin library so that when a Bitcoin transaction is being decoded, it is rejected if it tries to spend the same coin twice within the same transaction. This prevents a known bug class (CVE-2018-17144) where duplicate inputs could cause nodes to crash or accept invalid transactions. The change also updates existing tests that accidentally used duplicate inputs.

This commit adds a Rust compiler annotation called #[track_caller] to a single function. It does not change what the program does, how it validates inputs, or how it handles errors. It only improves the quality of panic messages so that if the function panics, the reported error location points to the caller's code rather than inside this library function. There is no security fix here.

This commit is purely a code-formatting run. It rewraps long lines, reorders imports, removes blank lines, and adjusts whitespace to match the project's style rules. No logic, behavior, or security checks were changed.

This commit only shortens a code comment to satisfy a Rust lint rule. No program logic, behavior, or security properties were changed.

This commit fixes example code and a test helper that builds Bitcoin Taproot script-path witness data. The old code placed digital signatures in the wrong order on the transaction witness stack, following the order of an internal sorted map instead of the reverse order required by the Bitcoin Taproot specification (BIP-0342). A transaction finalized with the old ordering would be rejected by the Bitcoin network, so no funds could be stolen, but users copying the example could produce invalid transactions. The fix reads public keys from the script in their actual script order, then pushes the matching signatures in reverse.

This commit adds new serialization/deserialization code for the Bitcoin P2P 'filteradd' bloom-filter message in the rust-bitcoin library. It is a routine feature implementation with no visible security bug, no fix of a vulnerability, and no disclosed security relevance.

This commit is a straightforward internal code cleanup in the Bitcoin peer-to-peer message handling code. It removes three thin wrapper types (CmpctBlock, GetBlockTxn, BlockTxn) and uses the underlying BIP-152 types directly in the main NetworkMessage enum. There is no functional change to how messages are parsed, serialized, or validated, and no security fix or vulnerability is present in the diff.

This commit adds convenience features to the Rust Bitcoin library so that a Bitcoin block header can be converted to and from a hexadecimal string. It does not fix a bug, change security behavior, or introduce a vulnerability. It is a normal feature addition.

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 only changes test code. It replaces the use of an external random number generator (from the `rand` crate) with a small, deterministic pseudo-random number generator inside the `MerkleBlock` unit tests. The goal is to make the tests reproducible and remove a test-only dependency on the `rand` feature. There is no change to production code and no security vulnerability is introduced or fixed.

This commit only adds and updates unit tests for relative locktime logic in the rust-bitcoin library. It does not change any production code, so it cannot introduce a security vulnerability or fix one directly.

This commit only adds new test cases to the rust-bitcoin library. It does not change any production code, fix bugs, or alter behavior. The tests cover edge cases for parsing numbers from strings, including uppercase hex prefixes and overflow cases. There is no security issue here.

This commit only adds new unit tests for the Sum trait on a Weight type. It does not change any production code, fix a bug, or alter behavior. There is no security relevance.

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 is a documentation and test fix, not a security patch. It adds a comment explaining that an 'empty coinbase' helper produces a 0-byte scriptSig that is technically invalid under Bitcoin consensus rules (which require 2-100 bytes), but is kept for backward compatibility in PSBT workflows where the scriptSig is filled in later. It also re-enables and updates a previously ignored unit test to use a valid 2-byte coinbase scriptSig.

This commit only adds new performance benchmarks to the project's benchmark suite. It does not change any production code, fix bugs, or alter security behavior. The benchmarks measure how long it takes to decode and validate Bitcoin blocks of various sizes, which is useful for future development decisions but has no direct security impact on its own.

This commit is a routine version bump for a small Rust library called bitcoin-io, from version 0.3.0 to 0.4.0-rc.0. It updates lockfiles, a changelog, and dependency references in other crates so they all use the new version. There is no code change and no security issue visible in the commit.

This commit only changes the package version number from 0.33.0-beta.1 to 0.33.0-beta.0 and updates the release date in the changelog. There are no code, logic, or dependency changes. It is purely a release bookkeeping adjustment with no security relevance.

This commit creates a brand-new Rust crate that simply defines which Bitcoin network a program is using (mainnet, testnet, signet, or regtest). It is a pure code-organization/refactoring change with no security relevance.

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 only updates an internal API test file to match recent changes in the `bitcoin_units` crate. It adds imports for newly introduced types (like `Sequence`), reorganizes existing ones, and includes new decoder/encoder types behind a feature flag. There is no change to production code, no bug fix, and no security relevance.

This commit adds a missing test helper that lets a library generate random relative locktime values for fuzz testing. It is not a security fix and does not change any runtime behavior of the Bitcoin library.