rust-bitcoin

This commit only adds performance benchmark tests for the SHA3-256 hashing code. It does not change any actual hashing logic, fix a bug, or alter security behavior. The commit message speculates that the existing implementation may perform poorly on small inputs, but this is an observation, not a security disclosure or patch.

This commit fixes a grammar mistake in a code comment, changing 'the' to 'they'. It has no effect on program behavior or security.

This commit fixes a single-letter typo in a code comment within an example file. The word 'to' was corrected to 'two' in the phrase 'these two calls.' There is no code change, no functional impact, and no security relevance.

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 spelling mistakes in code comments within an example file. The word 'where' is corrected to 'were'. There is no change to program logic, no security fix, and no functional impact.

This is a routine automated update by Dependabot that bumps the version of a GitHub Actions helper script used in a workflow that labels pull requests for semantic-versioning checks. There is no code change to the Rust Bitcoin library itself, and nothing in the commit suggests a security problem or fix.

This is a routine automated update by Dependabot that bumps the GitHub Actions 'labeler' workflow action from version 5 to version 6. It only affects how pull-request labels are managed and does not change any Bitcoin library code, cryptography, or user-facing behavior.

This is a trivial code cleanup in an embedded example. It removes an unnecessary .to_string() call on a hardcoded test string. There is no security relevance.

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.

This commit fixes a spelling mistake in a documentation comment, changing 'rror' to 'error'. It does not change any actual code or affect software behavior.

This commit is an automated code-formatting run by the rustfmt tool. It only changes whitespace, line breaks, import order, and brace placement. There are no functional changes to the Bitcoin library, and no security implications.

This commit only fixes a wrong word in a code comment. The example file's comment incorrectly said it constructs a 'p2wpkh' output and referred to a 'wpkh' variable, but the actual code builds a Taproot (p2tr) output using an 'internal_key' variable. No program code was changed, so there is no security impact.

This commit simply updates the version of the Rust nightly compiler used by the project's GitHub CI (continuous integration) tests from one weekly release to the next. It changes one line in a single configuration file and has no effect on the actual Bitcoin library code or its security.

This commit only refreshes an automatically-generated API listing file. It adds lines describing a new BlockTime encoder that already exists elsewhere in the codebase, but makes no code changes itself. There is nothing here that fixes, introduces, or hides a security problem.

This commit adds new helper types for combining small data encoders into larger ones when writing Bitcoin data. It is purely a code organization and feature addition change. There is no indication it fixes a security bug or introduces a vulnerability.

This commit refactors how Bitcoin block hashes are computed inside the rust-bitcoin library. Instead of manually feeding each block header field into the SHA-256 hashing engine one by one, the code now uses a shared 'pull-encoding' helper that walks through the header's encoded bytes and feeds them into the hash engine automatically. The change is a code-quality and maintainability improvement; there is no indication it fixes a security bug.

This commit is a routine internal refactoring in the rust-bitcoin library. It adds a new 'pull-based' encoding system for block headers and related types, replacing or supplementing older serialization code. There is no indication in the commit that this fixes a security bug, prevents an attack, or changes behavior visible to users in a risky way.

This commit adds new Rust traits and helper types for encoding Bitcoin data into bytes. It is purely a new internal API design change with no existing code using it yet, and it does not change any behavior that could affect security.

This commit fixes two spelling mistakes in a Markdown documentation file (`docs/keys.md`). It changes 'cryto' to 'crypto' and 'PriviateKey' to 'PrivateKey'. There are no code changes, no functional changes, and no security implications.

This is a trivial code-style cleanup. A developer replaced `self.data.len() == 0` with the equivalent but more idiomatic `self.data.as_slice().is_empty()`. The change only silences a Clippy lint and does not alter program behavior or fix any security issue.

This commit only removes documentation comments and two unused extern crate declarations from a Rust source file. It does not change any executable code, logic, or security behavior.

This commit adds a brand-new, empty placeholder Rust crate named `consensus_encoding` to the rust-bitcoin workspace. It contains no executable code, no traits yet, and no logic changes to existing crates. Its sole purpose is to reserve the package name on crates.io before someone else does. There is nothing here that could affect security.

This commit is a routine code cleanup that changes how internal items are imported within the rust-bitcoin library. It switches from importing through intermediate module paths to using crate-level re-exports. There is no functional change, no bug fix, and no security relevance.

This commit fixes two typos in documentation and deprecation messages: one in a code example comment and one in a deprecation note telling users which new method to use. There is no code behavior change and no security impact.

This commit only adds new test cases for the SHA3-256 hashing code. It does not change the actual hashing implementation, fix any bug, or alter how the library behaves in production. It simply verifies that the existing code produces the correct output for a set of standard test vectors from NIST.