rust-bitcoin

This commit is a simple internal code cleanup. It moves an error type (MessageSignatureError) from one place in the sign_message module into a new error submodule and re-exports it so users can still access it the same way. No behavior, logic, or security properties changed.

This change pins the version of a fuzzing tool used only in internal testing. It does not alter any code that end users run, and there is no indication it fixes a security vulnerability.

This commit is a routine code cleanup in the rust-bitcoin library. It replaces several manually-written decoder helper structs with a new macro that generates the same code automatically. There is no change to how data is parsed, no new behavior, and no security fix or vulnerability introduced.

This commit is a routine code cleanup in the rust-bitcoin library. It replaces several nearly identical decoder definitions with a single macro, reducing boilerplate. There is no change to user-facing behavior, no bug fix, and no security relevance.

This commit is a code clarity improvement only. It replaces empty default implementations of Rust's standard error trait with explicit implementations that return 'None' for the underlying cause. The behavior is identical before and after the change; it just makes the code easier to read for future maintainers.

This commit is a minor code cleanup with no security impact. It changes two Rust error types to explicitly state that they do not wrap another underlying error, instead of relying on the programming language's default behavior. The actual program behavior is unchanged.

This commit is a trivial documentation fix: it adds a single missing period to a public comment in the SHA256 error module. There is no code change and no security relevance.

This commit is a routine API cleanup: it renames the `PublicKey` type to `LegacyPublicKey` in the rust-bitcoin library and keeps `PublicKey` as a deprecated alias so existing code continues to compile. There is no bug fix, behavior change, or security patch in the diff.

This commit is a simple rename of a Rust type from CompressedPublicKey to FullPublicKey, with the old name kept as a deprecated alias. It does not change any behavior, cryptographic logic, or security properties. It is an API cleanup, not a security fix or vulnerability.

This commit only updates generated API snapshot text files for the rust-bitcoin primitives crate. It reflects a code reorganization where error types were moved into a new `error` submodule (for example, `bitcoin_primitives::block::ParseBlockError` became `bitcoin_primitives::block::error::ParseBlockError`). No actual source code, logic, or behavior changed, so there is no security impact.

This commit is a routine code cleanup in the rust-bitcoin library. It moves error type definitions for Bitcoin transactions into a new 'error' submodule and re-exports them, without changing what the errors mean or how transactions are validated. There is no security fix or behavior change.

This commit fixes a spelling mistake in an error message inside a maintainer helper script. The message previously said 'cargo-rmbt' when it should have said 'cargo-rbmt'. There is no change to program behavior, no security fix, and no risk to users of the library.

This commit is a refactoring of internal fuzz-testing code only. It changes how test inputs are generated for automated fuzzing targets, switching from a manual byte-slice approach to a newer automatic approach supported by the fuzzing library. It does not change any production Bitcoin parsing, validation, or networking code, and it does not fix or introduce any security vulnerability.

This commit only updates generated API snapshot files (text files listing public types and functions) to reflect that two error types were moved into new `error` submodules. No actual source code, logic, or behavior changed. It is a documentation/tracking update for the crate's public API surface and has no security relevance on its own.

This commit is a routine code reorganization. It moves the definition of an error type called MidstateError into a new 'error' submodule within the SHA256 code, then re-exports it at the original location so existing users are unaffected. There is no functional change to how the code behaves.

This commit only adds a website link (homepage metadata) to the package description files for all crates in the rust-bitcoin project. It does not change any code, logic, or security behavior. There is no security issue here.

This commit changes the default maximum decoded size for a compact-size length prefix from 4 MB to 32 MB in the rust-bitcoin library. To avoid accidentally allowing larger memory allocations, every existing place that used the old default is switched to an explicit 4 MB limit. The change is framed as matching Bitcoin Core's anti-DoS setting, not as fixing a known vulnerability. It could affect how downstream code behaves if it relied on the old 4 MB default without setting its own limit.

This commit adds new ways to create two existing decoder objects with a user-chosen size limit instead of the built-in 4 MB limit. The old default behavior is unchanged. There is no bug fix or security patch here; it is a small API convenience addition.

This commit only updates generated API snapshot files to reflect that two new public functions, `new_with_limit`, were added to existing decoder types. It contains no actual code changes, no bug fixes, and no security-related content.

This commit fixes a typo in a documentation comment. It changes the phrase 'to usually to encode' to 'to encode' in a source code file. There is no change to program logic, no security fix, and no functional impact.

This commit only moves existing code around. It reorders where certain `From<Infallible>` implementations and error trait implementations appear in the source files so they follow a consistent layout convention. No behavior, logic, or security properties of the code are changed.

This commit adds standard Rust traits (`Clone` and `Debug`) to a collection of data-encoding helper structs in the rust-bitcoin library. These traits let developers duplicate encoder/decoder objects and print them for debugging. There is no security vulnerability here; it is a routine API-quality improvement.

This commit simply adds the ability to duplicate (clone) several decoder helper objects in the Rust Bitcoin library. It is a routine feature addition with no security relevance visible in the code or commit message.

This commit adds a missing Debug formatting implementation for a six-element decoder helper in the Rust Bitcoin library. It is a routine code-quality fix with no security relevance.

This commit adds standard Rust helper traits (Debug and Clone) to a set of data encoder/decoder structs in the rust-bitcoin library. These traits only affect how developers can print, inspect, or duplicate encoder/decoder objects; they do not change serialization logic, parsing rules, or security behavior. There is no indication this fixes a vulnerability.