rust-bitcoin

This commit simply deletes redundant unit tests for encoding and decoding of Sequence, BlockHeight, and BlockTime. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The remaining error-handling tests still exercise the encoding feature.

This commit only adds a new test file that checks whether various Bitcoin data types can be correctly encoded to bytes and decoded back again. It does not change any production code, so it cannot introduce a security vulnerability or fix one.

This commit only changes the project's Clippy linter configuration file. It removes some general settings and tells the linter that 'SegWit' and 'OpenSSL' are valid terms in documentation so it won't nag about missing backticks. There is no code change and no security impact.

This commit is a routine update to the project's automated testing setup. It replaces a set of shell scripts with a new Rust tool called `cargo rbmt` for running tests and lints in CI. There are no changes to the actual Bitcoin library code that users interact with, and no security issue is evident.

This commit adds a single Rust lint suppression comment to silence a Clippy warning about a function having too many arguments. It does not change any executable code, behavior, or data flow. There is no security relevance.

This commit only adds Clippy lint-suppression attributes (`#[allow(clippy::too_many_arguments)]`) to three internal cryptographic helper functions in the `rust-bitcoin` hashes crate. It does not change any executable code, logic, or public API. There is no security relevance: it simply tells the Rust linter to stop warning that these functions have many parameters.

This commit adds new ways to encode and decode two Bitcoin peer-to-peer network messages, `GetBlocks` and `GetHeaders`. It does not change the existing encoding logic; it only introduces an alternative implementation using newer internal traits. There is no indication this fixes a security bug or introduces a vulnerability.

This commit only adds new unit tests for existing Bitcoin amount types. It does not change any production code, fix bugs, or alter behavior. There is no security relevance.

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 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 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 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.