rust-bitcoin

This commit only changes internal test code in the rust-bitcoin library. It replaces an unstable developer-only helper trait with a stable equivalent for converting hexadecimal strings into byte arrays. There is no change to production code, no user-facing behavior change, and no security fix.

This is a small internal code cleanup in the rust-bitcoin library. It changes how two hash-like types (transaction merkle node and witness merkle node) are encoded so that they reference existing data instead of making a copy. There is no security issue here—it's a performance/maintainability improvement that makes the code consistent with how other hash types are already encoded.

This commit only updates generated API text files that list which Rust traits (like Clone and Debug) are implemented by various types in the bitcoin_consensus_encoding crate. No actual source code, logic, or behavior changed. It is a documentation/maintenance update for the public API snapshot, not a security fix.

This commit adds standard Rust helper traits (Debug for printing, Clone for copying) to the library's byte encoders and decoders. It also adds a few new unit tests. There is no security fix or vulnerability here; it is a routine API-quality improvement.

This is a routine API cleanup, not a security fix. The change removes the requirement for callers to supply their own random number generator when creating a new keypair. Instead, the function now creates the generator internally, matching how the related PrivateKey API already works. There is no vulnerability here; it is a convenience and consistency change.

This commit only updates generated text files that list the public API surface of the Rust Bitcoin library. No actual source code, logic, or behavior changed. The files record that the `Block` type now carries a validation-state marker (`Unchecked`/`Checked`) and that some error types were added, but these are documentation artifacts, not a security patch.

This commit adds ordinary string formatting and hex parsing support for the Block type in a Rust Bitcoin library. It is a routine feature addition with no security relevance visible in the code or commit message.

This commit is a routine code cleanup. It relaxes unnecessary requirements on an internal helper type so that formatting a value as hexadecimal no longer requires the value to also be decodable. There is no security issue here.

This is a purely cosmetic code change. A developer added the word 'Unchecked' to an existing implementation line to make it clearer that this code path does not validate block contents. No program behavior, security checks, or logic were changed.

This is a cosmetic documentation-only change. It moves two error types from an inline re-export list to a separate non-inline re-export list, matching the project's existing style convention. There is no functional code change and no security impact.

This commit simply reorders two lines of Rust documentation import attributes. It moves an error type re-export to appear after inline type re-exports, with no functional code change. There is no security relevance.

This is a routine code-quality change in a Rust Bitcoin library. It adds and reorganizes implementations of `From<Infallible>` for certain hex-decoding error types. `Infallible` is a Rust type that can never actually be produced, so these conversions are only useful for making the type system happy and have no security impact.

This commit is a harmless code cleanup inside the project's test suite. It moves the creation of a fake Bitcoin block into a reusable helper function and renames a few variables. There is no change to the actual library code that users rely on, and no security implications.

This is a tiny code-quality change in how an error message is formatted. It replaces a debug-style error display with a more conventional human-readable error message. There is no security issue visible in the commit.

This commit is purely a housekeeping change in a Rust package configuration file. It reorders three optional dependency lines and adds a comment explaining that two of them are not meant to be used directly. There is no code change, no behavior change, and no security relevance.

This commit fixes a small bug in how Rust error chains are reported for two Bitcoin parsing error types. Previously, when asking 'what caused this error?', the code accidentally skipped past the immediate cause and returned the next level up. Now it correctly returns the immediate inner error. This is a correctness fix for error reporting and does not directly create a security vulnerability or allow attacks.

This commit adds a single Rust lint-suppression attribute to a test function so that the Clippy 'too_many_lines' warning is silenced. It does not change any runtime code, behavior, or security properties. It is purely a developer-experience change to keep CI passing after a toolchain update.

This commit only fixes how documentation appears for re-exported Rust modules. It changes some doc comments to regular comments and adds markers that control whether documentation is shown inline. There is no change to actual program logic, data handling, or security behavior.

This commit only adds new unit tests for an existing feature. It does not change any production code, fix a bug, or alter behavior. The tests verify that a decoder correctly accepts values at or below its configured limit and rejects values above it. There is no security issue here.

This commit adds standard encoding and decoding support for the Bitcoin P2P `addr` message payload (a list of network addresses). It is a routine feature addition that lets the library serialize and deserialize this message type. There is no indication in the commit that it fixes a security bug or introduces a vulnerability.

This commit adds new serialization/deserialization code for an existing Bitcoin peer-to-peer message type (AddrV1Message). It is a straightforward refactoring that implements the project's newer 'encoding' traits for a struct that already had older consensus encoding support. There is no indication of a security bug being fixed or introduced.

This commit is a straightforward internal code cleanup in the peer-to-peer networking module. It replaces an unnamed pair of values (a timestamp number and a network address) with a clearly named wrapper type called AddrV1Message. There is no change to security behavior, no bug fix, and no externally visible protocol change.

This commit creates a brand-new, empty placeholder crate named 'bitcoin-key-expression' inside the rust-bitcoin workspace. It contains no code, no logic, and no changes to existing behavior. It is purely a structural preparation step for future development.

This commit is a routine API cleanup, not a security fix. It changes one function so it takes its input by value instead of by reference, matching normal Rust conventions for small copyable types. There is no bug being fixed and no security relevance stated.

This commit is a small API cleanup in a Rust Bitcoin library. It changes one constructor so callers must provide a 'parity' value directly instead of setting it afterward. Existing callers are updated to preserve the same behavior as before. There is no indication this fixes a security bug or changes any security-relevant behavior.