rust-bitcoin

This commit only fixes two mistakes in code comments. One comment incorrectly named a previously called function, and another comment had a wrong arithmetic result for the maximum time value. No actual code behavior changes, so there is no security impact.

This commit adds standard encoding and decoding traits for the legacy Bitcoin P2P `Alert` message type in the rust-bitcoin library. It is a routine feature implementation that lets `Alert` be serialized and deserialized like other network messages. There is no indication in the commit or supplied references that this fixes a security bug or introduces a vulnerability.

This commit adds a new way to serialize and deserialize the Inventory message type used in Bitcoin peer-to-peer networking. It is a straightforward refactoring that mirrors the existing consensus encoding logic, moving it to a new internal encoding crate. There is no indication of a security bug being fixed or introduced.

This commit fixes a bug in a 256-bit unsigned integer multiplication routine used by the Rust Bitcoin library. The old code produced wrong multiplication results and failed to detect when the result exceeded 256 bits. Because this arithmetic is used in Bitcoin's difficulty retargeting calculations, incorrect results could theoretically lead to wrong difficulty estimates, though the practical attack path is limited.

This commit adds a Rust compiler hint called #[track_caller] to an internal helper function. It does not change program behavior, fix a bug, or alter any security boundary. It only improves the quality of panic/error location reporting if the code ever panics.

This is a minor change to a GitHub Actions CI workflow. It narrows the set of files included in a diff used by an automated mutation-testing tool (cargo-mutants) so that only Rust source files (*.rs) are considered. It does not change any production code, cryptographic logic, network handling, or user-facing behavior.

This commit adds new serialization/deserialization code for the Bitcoin P2P `UserAgent` field. It is a routine refactor that introduces a new internal encoding trait implementation alongside the existing one. There is no indication of a security bug in the change itself.

This commit adds a faster way to calculate SHA-256 hashes on modern 64-bit ARM processors (like Apple's M chips, AWS Graviton, and recent smartphones) by using built-in CPU instructions called ARM SHA2 crypto extensions. It mirrors an earlier change that did the same thing for x86 processors. There is no indication in the commit that this fixes a security bug; it is a performance improvement.

This commit adds new serialization/deserialization code for the `ProtocolVersion` type in the peer-to-peer networking module. It is a routine feature addition that mirrors existing patterns and does not fix any known bug or security issue.

This commit adds standard encoding and decoding support for ServiceFlags, a data type used in Bitcoin peer-to-peer messages. It is a routine feature addition with no visible security bug. The change simply lets the library serialize and deserialize ServiceFlags using a new internal encoding framework.

This commit fixes a bug where a specific PSBT error—'PsbtUtxoOutOfbounds'—was not handled during transaction extraction, causing the program to panic (crash) instead of returning a proper error. The fix makes the code treat this error the same as a missing UTXO, returning a controlled error message instead of hitting an 'unreachable' panic path. It is a robustness fix that prevents crashes when processing malformed or inconsistent PSBT data.

This is a routine performance improvement: it removes an unnecessary data copy when encoding an unchecked Bitcoin block. There is no security issue visible in the change.

This commit only changes test code in the rust-bitcoin project. It removes feature gates so that some merkle tree tests can run without the 'std' (standard library) feature. There is no change to production code, no security fix, and no vulnerability introduced.

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.