rust-bitcoin

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 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 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 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 removes an automated WebAssembly (WASM) test job from the project's continuous integration (CI) pipeline. The job tested only the 'hashes' sub-crate. The stated reason is that the job 'breaks all the time.' There is no code change to the library itself, and nothing in the commit suggests a security issue.

This commit only updates generated API text files that list what traits and methods are publicly available. It adds entries showing that a particular error type now implements standard Rust display and error traits. There is no code change, no bug fix, and no security relevance.

This commit is a routine code-quality fix. It adds the standard Rust error boilerplate (Display and std::error::Error implementations) to a missing-denomination error type and reorders similar boilerplate in another file. There is no security-relevant change.

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 only updates generated API text files that list what types and functions are publicly visible in the Rust library. It does not change any actual source code, behavior, or fix any problem. It is essentially a documentation refresh for the library's public interface.

This is a trivial code cleanup: it removes unnecessary 'core::' prefixes from formatting-related names in a Rust source file. The behavior of the program is unchanged, and there is no security relevance.

This commit only updates auto-generated API snapshot text files used to track the public Rust interface. It does not change any source code, behavior, or fix any bug. The files were regenerated with a tool (`just check-api`) so the recorded API matches recent code changes made in earlier commits. There is no security relevance.

This commit only updates generated API text files that list what traits and methods are publicly available in the library. No actual source code, logic, or behavior changed. It is a documentation/tracking update, not a security fix or vulnerability.

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

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 simply adds the standard Rust `Debug` trait to six empty marker types used for tagging different kinds of Bitcoin scripts. It is a routine, non-functional code-quality change with no security relevance.

This commit only updates generated API text files that list what types and functions are publicly visible in the library. It does not change any actual source code, behavior, or fix any problem. It is a documentation-like housekeeping change.

This commit simply removes an automated code-formatting check from the project's continuous integration (CI) pipeline and deletes the related contributor guidance. It does not change any library code, cryptographic logic, or network behavior, and it introduces no security vulnerability.

This commit simply adds the ability to duplicate (clone) a helper object called SighashCache that is used to speed up Bitcoin signature-hash calculations. It does not change any existing behavior, fix a bug, or alter security logic. There is no indication this is a security patch.

This is a routine cleanup of a GitHub Actions CI workflow. It removes one unused 'git fetch' step that was reportedly causing problems after code merges. There is no change to the actual Bitcoin library code, no security fix, and no vulnerability.