rust-bitcoin

This commit removes one obsolete Clippy lint rule from a project configuration file. Clippy is a Rust code-quality tool, not part of the actual Bitcoin library code. The change has no effect on program behavior, network handling, cryptography, or user data, and therefore has no security relevance.

This commit is a routine documentation and build-helper update. It adds a newly created Rust package (`bitcoin-consensus-encoding`) to the dependency tree generator script (`justfile`) and regenerates the `docs/dep-tree` file so the published diagram matches the project's actual crates. There is no code change, no bug fix, and no security relevance.

This commit is a routine code cleanup. It adds a `new()` constructor to a small helper type called `CompactSizeDecoder` and makes the existing `Default` implementation use that constructor. It does not change behavior, fix a bug, or address any security issue.

This is an automated code-formatting commit from rustfmt. It only changes whitespace and line breaks in two Rust source files. There is no functional change, no bug fix, and no security relevance.

This commit fixes a single grammar mistake in a documentation comment, changing 'it's' (with apostrophe, meaning 'it is') to 'its' (possessive). It does not change any executable code, behavior, or security properties.

This commit fixes a single typo in a documentation comment, changing 'available on at' to 'available at'. There is no code change and no security relevance.

This commit fixes a stray extra quotation mark in a documentation comment. It is a typo correction with no effect on program behavior or security.

This commit is a minor code-style cleanup in a Rust Bitcoin library. It changes one line in a verification test file, replacing a wildcard import ('use super::*') with two specific imports ('use super::{Amount, SignedAmount}'). There is no functional change to the library, no bug fix, and no security relevance.

This is a minor build hygiene fix. A Rust module that was only used behind an optional feature was triggering a compiler warning when that feature was disabled. The change simply hides the module unless the relevant feature is enabled, silencing the warning. There is no security relevance.

This is a documentation-only change that updates two import statements in code examples and tests from a deprecated module path to the current direct path. It does not alter any runtime behavior or security logic.

This is a trivial code cleanup that changes how a Rust lifetime is written to satisfy a clippy lint. It does not alter program behavior, fix a bug, or address any security issue.

This is a minor code cleanup that fixes a compiler warning (Clippy 'unused import') when tests are built with no default features. It does not change any behavior or fix any security issue.

This commit only adds two new unit tests to the project's custom I/O library. The tests check that a Cursor (a simple in-memory reader) behaves the same way as Rust's standard library when asked to read past the end of its data: it should return an empty buffer and allow the position to advance without error. There is no code change that fixes or changes behavior, and nothing here indicates a security issue.

This commit fixes a panic in a custom Cursor-like reader used by the rust-bitcoin project. Previously, reading past the end of a buffer could trigger an assertion failure (a crash). The fix makes the custom Cursor behave like Rust's standard library Cursor: it returns an empty slice when positioned past the end and avoids panicking when consuming bytes. This is a robustness fix that prevents denial-of-service-style crashes in code that reads untrusted or malformed data.

This commit is a test-only fix. The developers accidentally removed the lines that include separate test files for several hash modules (RIPEMD160, SHA1, SHA256, SHA512), meaning those tests were not being compiled or run. The commit re-adds those test modules and makes minor updates to the tests themselves so they compile with the current API. There is no change to production code and no security vulnerability is introduced or fixed.

This commit adds a new generic decoder in the rust-bitcoin library for reading lists of items from Bitcoin's wire format. It is a feature addition with tests, not a fix for a known bug or vulnerability. There is no indication in the commit message or diff that this addresses a security issue.

This commit adds a new decoder for reading length-prefixed byte vectors in the rust-bitcoin consensus encoding library. It includes a hard cap of 4,000,000 bytes to prevent attackers from tricking the decoder into allocating excessive memory. The change appears to be a routine feature addition with defensive limits already built in, not a fix for a known vulnerability.

This commit adds new serialization (encoding) helpers for Bitcoin transaction data types in the rust-bitcoin library. It is a feature/refactoring change that introduces an alternative way to convert transactions, inputs, outputs, and related types into bytes. There is no indication in the commit that it fixes a security bug, and the included tests pass. The main risk is that any new serialization code could contain subtle correctness bugs, but nothing in the diff points to an exploitable vulnerability.

This commit adds a small, routine Rust trait implementation that lets optional values be encoded in the same way as the values they wrap. There is no indication of a security bug or fix; it is a straightforward feature addition.

This commit adds a new way to serialize Bitcoin witness data into bytes. It is a straightforward feature addition with no visible bug fixes, no mention of security issues, and no changes to existing behavior. There is no indication this commit addresses a vulnerability.

This commit is a minor code cleanup in the rust-bitcoin library. It removes two unnecessary type casts inside a macro that converts fixed-size byte arrays into a 'PushBytesBuf' type used in Bitcoin script handling. The behavior of the code is unchanged; the casts were redundant because Rust automatically converts references to fixed-size arrays into references to slices.

This commit fixes two spelling mistakes: changing 'leafs' to 'leaves' in a code comment and adding the word 'the' in a rustfmt.toml comment. There are no code behavior changes, no security fixes, and no functional modifications.

This commit fixes a typo in a deprecation warning message. The warning previously told developers to use a non-existent function name (`get_ref()`) and now correctly points them to the actual function (`get_mut()`). It does not change any program behavior or fix a security issue.

This commit fixes two typos in a Markdown documentation file: the cryptographic crate name is corrected from 'chacha20_poly135' to 'chacha20_poly1305', and a broken link reference is corrected from 'address.md' to 'addresses.md'. There are no code changes and no security implications.

This commit adds a new decoder for Bitcoin's 'compact size' integer format in the rust-bitcoin library. It is a feature addition, not a fix for a known security bug. The code carefully checks for non-minimal encodings (a common source of parsing bugs in Bitcoin) and includes unit tests. There is no indication in the commit or supplied references that this resolves a disclosed vulnerability.