rust-bitcoin

This commit is a routine performance improvement, not a security fix. It adds a new way to get an opcode's name as a static string slice without allocating memory, and uses that new method during JSON/serde serialization. There is no change to behavior, no bug fix, and no security relevance in the code itself.

This commit adds a new CI test script that checks whether all public items from one Rust crate (bitcoin_units) are correctly re-exported in another crate (bitcoin_primitives). It does not change any library code, only adds a build/verification script and a GitHub Actions job. There is no security issue here.

This is an automated code-formatting commit from rustfmt. It only changes whitespace, line breaks, and import ordering. There is no functional change and no security relevance.

This commit only adds two new unit tests for existing XOnlyPublicKey functions. It does not change any production code, fix bugs, or alter behavior. There is no security issue here.

This commit adds a simple accessor method that lets users extract the underlying cryptographic key from a wrapper type. It is a routine API addition with no security relevance visible in the code or commit message.

This change only adds a Clippy lint warning in the benchmark crate's configuration. It tells the Rust linter to warn when code could use `Self` instead of repeating the type name. It does not change any executable code, fix any bug, or affect the library's behavior or security.

This commit is a routine code-quality cleanup. It turns on a Rust linter rule (clippy::use_self) that encourages using 'Self' instead of repeating a type's name inside its own implementation blocks, and updates the affected code to satisfy the new rule. There is no functional change, no bug fix, and no security relevance.

This commit adds a code-style lint (a Clippy warning) to the fuzz testing crate. It tells developers to prefer `Self` over repeating the type name in implementations. There is no change to runtime code, no bug fix, and no security relevance.

This commit is a code-style cleanup in the rust-bitcoin library's units crate. It enables a Clippy lint called use_self and replaces explicit type names (like FeeRate, Weight, LockTime) with the shorthand Self inside impl blocks. These changes do not alter program behavior, fix no bugs, and have no security relevance.

This commit is a minor code-style cleanup in the base58 subcrate. It turns on a Clippy lint that encourages using 'Self' instead of the type name when calling functions inside an implementation block, and updates two function calls to match. There is no change to behavior, no bug fix, and no security relevance.

This commit only changes style: it replaces explicit type names like Key or Nonce with the Rust shorthand Self inside the same type's implementation block, and adds a Clippy lint to warn about this style in the future. There is no change to program behavior, no bug fix, and no security relevance.

This commit is purely a code-style cleanup. It turns on a Clippy lint that encourages using 'Self' instead of repeating type names inside Rust code, then updates many files in the rust-bitcoin hashes crate to follow that style. There is no functional change, no bug fix, and no security impact.

This commit only turns on a code-style lint (clippy::use_self) and makes two tiny style changes so the code passes the new lint. It does not change behavior, fix a bug, or address any security issue.

This commit only adds a Clippy lint configuration to warn when code uses a type's full name instead of `Self`. It makes no changes to executable code, APIs, or security behavior. There is no security relevance.

This commit only turns on a code-style lint (clippy::use_self) and updates a few return types and constructor calls to use the preferred 'Self' shorthand. It does not change behavior, fix a bug, or alter any security-relevant logic.

This commit only turns on a Rust style lint (clippy::use_self) and rewrites code to use `Self` instead of repeating type names. It does not change any behavior, logic, or security properties of the library.

This commit is a purely cosmetic code cleanup. It enables a Rust linter rule (clippy::use_self) that encourages using 'Self' instead of repeating type names inside implementations. The changes only rename type references and do not alter program behavior, data formats, or security checks.

This commit only turns on a Rust style lint (clippy::use_self) and replaces explicit type names with `Self` in the source code. It does not change what the code does, only how it is written. There is no security impact.

This commit is a routine performance and ergonomics improvement. It changes several Rust constructor functions from regular functions to 'const' functions, which lets the compiler precompute some values at compile time rather than runtime. There is no change to security behavior, no bug fix, and no vulnerability patch.

This commit adds public API snapshot files for the consensus_encoding crate and updates a script to include that crate in API change checks. It is purely a tooling and documentation change that records what functions and types are currently exposed to users. There is no change to actual program logic, no bug fix, and no security patch.

This is a routine update to a CI (Continuous Integration) tool version. It changes the version of cargo-public-api used in automated checks from 0.49.0 to 0.50.1, because the older version does not support a Rust language feature called macro_export that the project now uses. There is no security relevance.

This commit only changes three lines of documentation comments for a Cursor type. It updates the description to mention that the position tracking applies to both reading and writing. There is no code change, no behavior change, and no security relevance.

This commit adds a new helper function that lets no-std code write encoded Bitcoin data to custom I/O writers. It is a straightforward feature addition mirroring an existing std-only helper. There is no indication of a security bug, fix, or vulnerability.

This commit adds a normal feature: it lets a Cursor (a wrapper that tracks your position while reading/writing a byte buffer) support writing, not just reading. The implementation matches the standard Rust library pattern and includes unit tests. There is no indication this fixes a bug or addresses a security issue.

This commit is a routine code cleanup that renames some internal conversion functions on the Address type to follow Rust naming conventions. It does not change what the code does, only what the functions are called. The old names are kept as aliases that show a deprecation warning so existing users are not broken.