rust-bitcoin

This commit only adds new unit tests for an existing Bitcoin hash type. It does not change any production code, so it cannot introduce or fix a security vulnerability on its own.

This commit only adds a new unit test to verify that different ways of reading a transaction hash (Txid) return the same underlying bytes. It does not change any production code, APIs, or behavior. There is no security relevance.

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

This commit is a minor internal test cleanup. It moves a hard-coded dummy transaction ID string used only in unit tests into a constant so it can be reused in future tests. There is no change to production code, no security fix, and no user-facing behavior change.

This commit only adds two new automated tests for the block hash decoder. It does not change any production code, so it cannot introduce or fix a security vulnerability on its own.

This commit only changes the project's GitHub Actions CI configuration to add automated cross-compilation testing for the aarch64 (64-bit ARM) Linux target, alongside the existing s390x target. It does not modify any library code, cryptographic logic, or user-facing behavior. There is no security issue here.

This commit adds new serialization/deserialization code for the Bitcoin P2P 'reject' message using the project's newer encoding framework. It is a routine refactor/migration of an existing message type to a new encoder/decoder API. There is no indication in the commit or supplied references that this fixes a security bug, vulnerability, or crash.

This commit adds new encoding/decoding machinery for the RejectReason type used in Bitcoin peer-to-peer messages. It does not change existing behavior or fix any known bug; it is a routine feature addition that makes the type work with a newer internal encoding framework. There is no indication of a security issue.

This commit adds new encoding and decoding machinery for a Bitcoin peer-to-peer message type (BlockTransactionsRequest). It is a routine feature addition that mirrors an existing implementation and does not appear to fix or introduce a security problem on its own.

This commit refactors how Bitcoin compact-block transaction indexes are stored and encoded. It replaces a public Vec<u64> field with a private Vec<Offset> field and adds constructors that require callers to provide sorted indices. The change removes a documented panic during serialization when u64::MAX was used, and moves overflow detection from encoding time to a new indices() accessor. It is a defensive hardening patch rather than a clear-cut vulnerability fix, because the previous panic required a caller to deliberately construct an invalid object and then serialize it.

This commit only changes how Rust documentation is generated for certain error types. It switches some re-exports from being shown as if they were defined in the current module to being shown as re-exports from another module. There is no change to actual code behavior, no security fix, and no vulnerability.

This commit adds a new decoder for Bitcoin peer-to-peer network message headers in the rust-bitcoin library. It is a straightforward feature addition that exposes a way to parse v1 message headers using the existing consensus encoding framework. There is no indication of a security bug, fix, or vulnerability.

This commit adds a new way to encode and decode the Bitcoin 'filterload' P2P network message using a new internal encoding framework. It is a routine refactor that mirrors how other message types were already handled. There is no indication of a security bug being fixed or introduced.

This commit adds new encoding helpers for a small network-message flag type called BloomFlags. It does not change existing behavior; it only wires up a new internal encoding trait implementation and improves an error message to report the actual unknown flag value. There is no indication this fixes or introduces a security issue.

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

This commit only adds a new unit test. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The test verifies that certain difficulty-target constants in the rust-bitcoin library match the values used in Bitcoin Core after a compact/lossy conversion.

This commit is a routine internal code reorganization. It removes the definitions of Bitcoin network types (like Mainnet, Testnet, Signet) from the main `bitcoin` crate and instead re-exports them from a new dedicated `bitcoin-network-kind` crate. It also adds fallback handling for any future testnet versions. There is no indication this fixes a security vulnerability.

This commit is a routine internal code reorganization. It moves some methods of the Network type into a new 'extension trait' called NetworkExt so that the underlying Network type can be shared with a separate crate. There is no security bug being fixed here.

This commit only changes documentation comments (docstrings) for several constants in the proof-of-work module. It rewords descriptions to be consistent and adds a source reference comment. No code behavior is altered, so there is no security impact.

This commit only adds a documentation link inside a code comment. It does not change any executable code, behavior, or security properties of the library.

This commit is a routine code-quality refactor in the rust-bitcoin library. It wraps the underlying secp256k1 keypair type in a library-specific type so that parsing errors can be more precise and the public API is cleaner. There is no direct security vulnerability being fixed here; it is an interface improvement that may indirectly reduce misuse.

This commit is a routine code refactoring in the rust-bitcoin library. It splits the existing difficulty calculation functions into two parts: new lower-level functions that take a maximum target directly, and the original functions that now simply call these new functions with the network's maximum target from the Params object. There is no change to the actual math or behavior, and no security issue is present.

This commit is purely a code-formatting cleanup performed by an automated rustfmt nightly run. It reorders imports, collapses or expands brace blocks, removes blank lines, and adjusts line wrapping in test code. No program logic, APIs, or security behavior was changed.

This commit changes how the Rust Bitcoin library allocates memory when decoding a Bitcoin transaction's witness data. Previously, the decoder could double its internal buffer repeatedly, which could let a maliciously crafted transaction force the program to reserve far more memory than needed. The new code allocates memory in roughly 1 MB batches instead. A test was added that feeds a 4,000,000-element witness and checks that the decoder only allocates about 16–17.5 MB, suggesting the change is meant to limit memory blow-up during decoding.

This commit only adds a new unit test. It does not change any production code. The test checks that the library rejects Bitcoin transactions containing an output worth more than the maximum allowed money (MAX_MONEY + 1 satoshi) when decoding transaction bytes. It is a defensive test borrowed from Bitcoin Core's test data, confirming an existing safety check works.