rust-bitcoin

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 simply updates the version (commit hash) of an internal GitHub Actions helper tool used in the project's continuous integration (CI) pipelines. There is no change to the actual Rust Bitcoin library code, no user-facing behavior change, and no security fix or vulnerability patch visible in the diff.

This is a purely cosmetic code-formatting change made by an automated rustfmt tool. It rewrites one type alias definition in a single file to fit on fewer lines. There is no functional change, no bug fix, and no security relevance.

This commit updates formal verification tests (Kani proofs) for CompactSize encoding. It does not change any production code. The change makes the proofs check that oversized values are correctly rejected, rather than checking round-trips for very large values. There is no indication this fixes a security bug in the actual library.

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. It moves several error type definitions from the main block module into a new `error` submodule and adjusts how those error types are publicly re-exported. There is no change to how blocks are validated, parsed, or encoded, and no security bug is fixed.

This commit is a simple internal code reorganization. It moves two error types (WitnessDecoderError and UnexpectedEofError) from the main witness module into a new error submodule and re-exports them so existing code keeps working. There is no functional change to how witness data is decoded or validated.

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 is a routine code cleanup with no security relevance. It moves Bitcoin script error types into a dedicated 'error' submodule and re-exports them so the public API stays the same. There are no functional changes to how scripts are parsed, validated, or executed.

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 simply adds standard Rust helper traits (Debug for printing and Clone for copying) to a large set of P2P message encoder and decoder types. It does not change any behavior, parsing logic, or security checks. There is no security issue here.

This commit is a simple internal code reorganization. It moves the existing 'Error' type into a new 'error' submodule and re-exports it so users can still access it the same way. There is no change to how encryption, decryption, or authentication works, and no security bug is fixed or introduced.

This commit changes a documentation-only Rust attribute on public error re-exports. It tells the documentation generator not to inline the details of these error types on the crate's main page. There is no change to executable code, behavior, or security.

This commit is a routine code reorganization. It moves an existing error type (MaxLengthError) from the main HKDF module into a new 'error' submodule and re-exports it publicly. There is no functional change to how the code behaves, no bug fix, and no security improvement or regression.

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 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 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 is a routine automated update that changes the recorded stable Rust compiler version in the project's configuration file from 1.93.1 to 1.94.1. It does not modify any source code, dependencies, or security-sensitive settings. There is no indication of a security fix or vulnerability.

This commit removes an explicit 4-million-item size limit when decoding two compact-size numbers in Bitcoin compact block (BIP-152) messages. The author argues the limit is unnecessary because the decoded values are ultimately stored as 16-bit unsigned integers (u16), so any value larger than 65,535 will already be rejected later in the decoding process. The change is a code simplification rather than a clear security fix, but it slightly shifts where and how oversized inputs are rejected.

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