rust-bitcoin

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 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 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 only changes wording in documentation comments and one inline code comment. It renames 'Secp256k1' to 'secp256k1' and expands the shorthand 'secp' to 'secp256k1' for consistency. No executable code, logic, cryptography, or APIs were modified, so there is no security impact.

This commit only improves the wording of error messages shown when tests fail. It does not change any production code, behavior, or security logic.

This commit only removes extra spaces inside comments and a user-facing error message string. It does not change any executable code, logic, or behavior. There is no security relevance.

This commit fixes two spelling/grammar mistakes in code comments and documentation strings within a Bitcoin signature hashing file. There are no code behavior changes, no bug fixes, and no security implications.

This commit is a routine internal code cleanup in the rust-bitcoin library. It changes an encoding helper function so that it returns an empty byte slice instead of a special 'no value' (None) marker when there is nothing left to encode. The behavior of the code is intended to stay the same; only the way callers check for the end of data is simplified. There is no indication this fixes a security bug.

This is an automated code-formatting commit from rustfmt. It only changes whitespace, line breaks, import order, and other stylistic details. There are no functional changes and no security implications.

This commit only fixes grammar in code comments and renames a test function that had a typo in its name. There are no code behavior changes, no security fixes, and no functional patches.

This commit fixes a spelling mistake in two documentation files, changing 'sciptcode' to 'scriptcode'. It does not change any code, program behavior, or security properties.

This is a minor code-quality change. A constant used only in tests that require the 'alloc' feature was not itself behind that feature gate, causing a compiler warning (Clippy lint) when building without that feature. The patch adds the missing feature gate so the constant is only compiled when needed. There is no security impact.

This commit is a routine code-quality fix. It adds Rust feature gates so that certain test-only structs and imports are only compiled when the 'alloc' feature is enabled, silencing a Clippy warning about structs that are never constructed. There is 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 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 fixes two typos in comments/constant names within PSBT serialization code. One renames a local constant from PSBT_SERPARATOR to PSBT_SEPARATOR (the value 0xff is unchanged), and the other fixes a grammar error in a comment. Neither change alters program behavior.

This commit fixes a single-letter spelling mistake in an error message string: 'deserializaton' is corrected to 'deserialization'. It does not change any program logic, parsing behavior, or security properties.

This commit only adds new performance benchmark tests for the ChaCha20-Poly1305 encryption code. It does not change any production code, fix any bug, or alter any security behavior. There is no security issue here.

This commit fixes three English grammar typos in comments and user-facing error messages within the Partially Signed Bitcoin Transaction (PSBT) module. It changes 'an non-ECDSA' to 'a non-ECDSA' and 'an ripemd160' to 'a ripemd160'. There are no code logic changes.

This commit is a routine refactoring that moves hash benchmarking code from inside the main source files into a separate benchmark suite using the Criterion library. It does not change how the hashing functions work, what data they process, or how they are exposed to users. There is no security fix or vulnerability here.

This commit only changes the wording of code documentation comments (rustdoc) from imperative to third-person style (e.g., 'Parse' to 'Parses'). It also adds a project policy note about this documentation style. No executable code, logic, or behavior was modified, so it has no security impact.

This commit is a purely cosmetic documentation and comment change. It rewrites Bitcoin Improvement Proposal (BIP) references from formats like 'BIP-32' or 'BIP 68' to a new standardized four-digit format like 'BIP-0032' or 'BIP-0068' across changelogs, examples, source code comments, and markdown docs. No program logic, code behavior, or security properties were changed.

This commit only reformats documentation comments. It changes how web links to Bitcoin Improvement Proposals (BIPs) are written in source-code documentation, moving the actual URL to the bottom of the doc block rather than embedding it inline. No program logic, math, cryptography, or transaction handling code is modified.

This commit fixes a typo in an example program's error message. The message previously told users to call a non-existent function; now it points to the correct function name. There is no security issue.

This commit fixes two typos in code comments within an example file. One misspelled word ('scep' instead of 'secp') and one grammar issue ('an watch-only' instead of 'a watch-only') were corrected. There are no code behavior changes, no security fixes, and no functional impact.