rust-bitcoin

This commit is a simple internal code cleanup. It moves a small helper type used only for formatting debug output from a shared internal utility module directly into the only place it is used, then removes the now-unused utility module. There is no change to how the code behaves or to any security-sensitive logic.

This commit is a routine code cleanup: it moves a small test-only helper macro from a shared internal utility crate into the one place it is actually used. There is no change to user-facing behavior, no bug fix, and no security relevance.

This commit is a pure code reorganization: it moves existing implementations of string formatting, hex display, encoding, and decoding for Bitcoin transactions into a different order within the same file. No logic was changed, no bugs were fixed, and no security behavior was altered.

This commit only moves existing code around in four source files. It reorders the encoding and decoding definitions so they follow the same pattern across the project. No logic was changed, no bugs were fixed, and no security issue is present.

This commit simply stops publicly re-exporting a secp256k1 type called `Verification` from two Rust Bitcoin key modules. It is a routine API cleanup: the type is still available directly from the underlying secp256k1 library, so no cryptographic capability is removed, only a convenience shortcut. There is no security bug or vulnerability here.

This commit only updates project documentation (docs/policy.md). It removes a recommendation to use a third-party 'ordered' crate and instead cautions developers about deriving standard Rust ordering traits on enums because variant order becomes part of the public API. There is no code change and no security fix or vulnerability introduced.

This commit only adds two documentation comments to clarify that hex strings passed to certain Weight constructors are interpreted as weight units. There are no code changes, no behavior changes, and no security implications.

This commit fixes a single-word typo in a documentation comment. The function takes an Amount type, but the comment incorrectly said 'satoshis'. There is no code change and no security impact.

This commit only adds or removes blank lines between constant definitions in four source files to make the code style consistent. It does not change any program logic, values, or behavior, so it has no security relevance.

This commit only changes two documentation comments in the rust-bitcoin library to use a consistent style for writing the number 1000 (with a comma as '1,000'). It does not modify any executable code, logic, or data handling.

This commit only changes the letter case of a variable name in documentation comments, from uppercase 'T' to lowercase 't'. It is a purely cosmetic documentation edit with no effect on code behavior or security.

This commit simply reorders module declarations in a Rust source file so that private modules are listed before public ones. It makes no functional changes to the code and has no security relevance.

This is a one-line documentation-only change in the Rust Bitcoin library. It adds a Rust attribute that prevents a re-exported error type from being shown as inlined in generated API documentation. There is no change to executable code, behavior, or security.

This is a one-word documentation fix in a Rust Bitcoin library comment. It corrects a typo in the user-facing documentation for the FeeRate type, changing 'from_sat_per*' to 'to_sat_per*' so the described function names match the actual API. There is no code change and no security impact.

This commit simply deletes two unit tests that checked deprecated functions still forwarded to their replacements. No production code was changed, so it cannot introduce or fix a security issue on its own.

This commit removes old, deprecated function names and type aliases from the rust-bitcoin `units` crate in preparation for a 1.0.0 release. It is a routine API cleanup: no security bug is fixed and no new unsafe code is added. Downstream projects that still use the removed names will get compile-time errors and must switch to the replacement APIs.

This commit only updates generated text files that list the public API surface of the library. No actual source code, logic, or behavior changed. It is not a security fix and does not introduce or remove any vulnerability.

This is a small cleanup change inside test code only. It replaces a deprecated method call with a modern equivalent and tidies up an import. There is no security issue here.

This commit is a routine code cleanup in the rust-bitcoin library. It replaces generic error types from the underlying secp256k1 cryptographic library with more specific, library-defined error types for key parsing and signature verification functions. There is no indication this fixes a security vulnerability; it is an API-quality improvement.

This commit is a straightforward internal cleanup in the rust-bitcoin library. It swaps one error type for another when an ECDSA signature fails to decode from DER format. The behavior of signature parsing does not change; only the name and contents of the error value reported to callers are different. There is no indication this fixes a security bug or introduces a vulnerability.

This commit is a routine internal code cleanup in the rust-bitcoin library. It removes a convenience conversion (a 'From' implementation) between two error types and replaces it with an explicit error mapping. The actual behavior of signature parsing does not change; it is purely about how errors are wired through the code. There is no indication this fixes a security bug.

This commit removes an unused error category from a Bitcoin cryptography library. It is a cleanup change because the underlying signature-parsing code can no longer fail in the way that error category described. There is no direct evidence this fixes an active security bug, but it does slightly reduce the library's public error surface, which can help downstream code handle errors more reliably.

This commit is a routine code-quality refactor. It introduces new, more specific Rust error types for parsing keys and signatures, replacing a generic underlying library error type. There is no change to cryptographic behavior, validation logic, or security boundaries. It only changes what kind of error message callers receive when parsing fails.

This commit only updates generated API snapshot files (text listings of public functions) for the consensus_encoding crate. It adds entries for three new public functions that decode data using an explicit decoder type. There is no source code change, no bug fix, and no security relevance visible in the diff.

This commit adds new public helper functions to a Rust Bitcoin encoding library. The functions let callers decode data using a decoder type directly, rather than only through types that implement a specific trait. It is a pure API convenience addition and does not change existing behavior or fix any bug.