rust-bitcoin

This commit is a routine code cleanup. It removes unnecessary '?' operators in functions that already return a Result. The behavior of the code is unchanged; it just makes the code slightly cleaner and avoids a clippy lint warning.

This commit is a routine code cleanup in the Rust Bitcoin library. It rewrites a few internal helper methods to use more idiomatic Rust syntax (Option methods and pattern matching) instead of longer if/else blocks. There is no change to what the code actually does, no security fix, and no bug being patched.

This commit only updates the project's SECURITY.md policy document. It changes the list of covered items from individual Rust crates to whole GitHub repositories, removes a mention of cryptography, and adds two additional repositories (rust-bech32 and hex-conservative) to the security policy. No code, logic, or cryptographic behavior was changed, so there is no security vulnerability or fix in the commit itself.

This commit is a routine cleanup of build configuration files. It removes two text files that previously stored Rust compiler version numbers and updates one CI workflow to read the same version information from project metadata instead. There is no security relevance.

This commit is a pure code cleanup: it reorders where certain trait implementations (like FromStr, From, Display, Debug) appear in the source file so all types follow the same consistent pattern. No code behavior is changed, no security bug is fixed, and no vulnerability is introduced.

This commit simply moves the code that handles serializing and deserializing XOnlyPublicKey values (when the optional serde feature is enabled) from one location in the file to another location alongside similar implementations. The actual behavior of the code is unchanged; it is a pure code organization or cleanup change with no security relevance.

This commit removes a convenience conversion that let users turn a Bitcoin-style key pair directly into a lower-level secp256k1 public key. The change is defensive: it makes it slightly harder to accidentally mix the library's own key types with raw secp256k1 types, which can help prevent API misuse. There is no direct bug or exploit being fixed.

This commit adds standard Rust helper code that lets several error types be automatically converted from Rust's Infallible type. Infallible is a type that can never actually exist, so these conversions are safe, cannot be triggered by user input, and have no security impact. It is a routine API ergonomics improvement.

This commit only changes placeholder version strings ('TBD') in deprecation notices to a concrete version number ('0.1.0'). It does not alter any program logic, cryptographic operations, or security behavior. There is no security impact.

This commit is a pure code reorganization: it moves existing Rust 'From' conversion implementations so they sit directly underneath the type they produce, rather than being scattered near the source type. No logic, behavior, or public API changes are visible in the diff.

This commit only adds the #[inline] compiler hint to many small functions in the cryptographic key module. It does not change what any function does, what data it accepts, or how secrets are handled. There is no security bug being fixed or introduced here; it is a routine performance optimization.

This is a small internal code cleanup in the rust-bitcoin library. It replaces a slightly longer implementation of converting one public key type to another with a shorter one that calls an existing conversion. There is no change in behavior and no security issue.

This commit simply moves an existing implementation of the Drop trait for the Keypair type to a different location in the same source file. It does not change what the code does, only where it appears in the file. There is no security impact.

This commit is a simple code cleanup with no security relevance. It replaces long-form calls like `fmt::Display::fmt(value, formatter)` with shorter `value.fmt(formatter)` calls inside formatting trait implementations. The behavior is identical; only the syntax is shorter.

This commit simply updates a dependency version number used only in fuzz testing infrastructure. It changes the pinned version of an older 'bitcoin' crate from 0.32.8 to 0.32.9 in lock files and fuzz configuration files. There is no indication this is a security fix for the main project, nor does the commit itself describe any security relevance.

This commit fixes how the rust-bitcoin library handles malformed 'fee filter' messages from the Bitcoin peer-to-peer network. Previously, out-of-range fee values were silently clamped to the maximum allowed rate, which could make messages fail to 'round-trip' (encode back to the same bytes) and could subtly corrupt checksum calculations. Now those invalid values cause a clear decoding error instead, matching the behavior of Bitcoin Core.

This commit only changes a fuzz testing target. It tells the fuzzer to ignore certain known, expected differences between old and new Bitcoin encoding/decoding code. It does not change the actual library code that handles transactions, addresses, or network messages, so it cannot directly affect real users or introduce a security vulnerability.

This commit fixes a regression in the Bitcoin peer-to-peer address decoder. A recent rewrite accidentally stopped rejecting oversized network addresses (over 512 bytes), which could let malformed or unusually large data pass through as an unknown address type. The patch restores the original safety check that rejects such oversized inputs with an explicit error.

This is a tiny build-configuration cleanup. It removes a non-existent feature flag ('hashes/arbitrary') from a list of features that get enabled when the 'arbitrary' feature is turned on in the taproot-primitives crate. The flag pointed to a feature that does not exist in the hashes crate, so it had no effect and could not cause a security problem. The change simply prevents a harmless misconfiguration.

This is a one-line fix to a code example so it uses a configurable network parameter instead of always using the regtest network. It is not a security fix and does not change any library behavior.

This change improves error messages when decoding Bitcoin peer-to-peer network messages. Previously, if the message header failed to decode, the higher-level decoder would report a generic 'header error' with no details. Now it wraps and preserves the underlying header decoder error so callers can see what specifically went wrong. There is no security vulnerability being fixed here; it is a usability and diagnostics improvement.

This is a small internal code cleanup in the Bitcoin peer-to-peer message decoder. It replaces a hand-built four-part header decoder with an existing dedicated header decoder. There is no security bug being fixed; the change is purely for code reuse and slightly better error messages.

This commit is a small internal code cleanup in the Bitcoin peer-to-peer message decoder. It changes how message length and network magic bytes are stored while being parsed, switching from raw byte arrays to already-parsed types. There is no security fix here; it is purely a refactoring to simplify the code and make future maintenance easier.

This commit only changes a fuzz testing target so it ignores additional known differences between old and new Bitcoin data decoders. It is a test-configuration update, not a fix to production code, and does not change how real transactions are validated.

This commit adds a single formatting directive (`#[rustfmt::skip]`) to tell Rust's automatic code formatter not to reformat a specific SHA-256 hashing function. It does not change any executable code, logic, or behavior. There is no security impact.