rust-bitcoin

This commit refactors how Bitcoin peer-to-peer messages request blocks and headers. It replaces a plain list of block hashes with a dedicated 'BlockLocator' type and adds a helper to build locators in a logarithmic pattern (like Bitcoin Core). There is no direct security fix here; it is a structural improvement that makes the library behave more like Bitcoin Core and could indirectly reduce network/DoS risks by capping locator size and producing better locators.

This is a small internal cleanup change in the rust-bitcoin library. It swaps some low-level uses of one public-key type for another equivalent type that now carries extra parity information. There is no indication this fixes a security bug or changes behavior visible to users in a risky way.

This commit is a routine internal API cleanup in the rust-bitcoin library. It changes one function so it accepts the project's own public-key type instead of a lower-level secp256k1 public-key type, removing unnecessary conversions at call sites. There is no indication this fixes a security bug or introduces a vulnerability.

This commit is a purely cosmetic refactoring of Rust conditional-compilation attributes. It splits combined `#[cfg(all(...))]` expressions into two stacked `#[cfg(...)]` attributes, which is a supported Rust syntax and does not change which code gets compiled under which conditions. There is no security relevance.

This commit is a purely stylistic change in the Rust Bitcoin library. It rewrites conditional compilation attributes (the Rust equivalent of #ifdef feature flags) from a single combined form to a stacked form. For example, #[cfg(all(feature = "hex", feature = "alloc"))] becomes two separate #[cfg(...)] lines. This has no effect on which code is compiled or how the library behaves, and it does not fix or introduce any security issue.

This commit is a purely stylistic cleanup in the Rust Bitcoin library. It changes how the code tells the compiler which optional features must be enabled for certain pieces of code to compile, switching from combined conditions like `#[cfg(all(feature = "std", feature = "encoding"))]` to stacked single conditions like `#[cfg(feature = "std")]` followed by `#[cfg(feature = "encoding")]`. In Rust, these two forms mean the same thing, so this does not change behavior, fix a bug, or address a security issue.

This commit only adds a coding-style rule to the project's documentation. It tells developers to prefer stacking multiple #[cfg] attributes instead of combining them with #[cfg(all(...))]. No code behavior changed, and there is no security impact.

This commit is a purely cosmetic change in how Rust conditional compilation rules are written. It splits combined conditions like `cfg(all(A, B))` into two separate stacked `#[cfg(A)]` and `#[cfg(B)]` lines. The actual conditions and the resulting compiled code are unchanged, so there is no security or functional effect.

This commit is a minor Rust code cleanup. It changes one line that previously required both the 'std' and 'alloc' features together into two separate feature checks stacked on top of each other. There is no functional or security change; the compiled result is the same.

This commit is a minor code-style change in the Rust Bitcoin library. It rewrites a single conditional compilation attribute from one combined form into two stacked forms. There is no functional change, no bug fix, and no security relevance.

This commit is a code-style refactor. It replaces single-line Rust conditional annotations like #[cfg(all(A, B))] with stacked separate lines like #[cfg(A)] #[cfg(B)]. The behavior is identical; no security issue is introduced or fixed.

This commit is a routine internal refactoring of the rust-bitcoin project. It moves a helper macro called transparent_newtype from one internal crate to a shared include file, then updates all crates to use the shared version. There is no change to user-facing behavior, no bug fix, and no security relevance.

This commit only fixes the wording and formatting of documentation comments in four source files. It adds backticks around hash function names like `SHA256d` and `SipHash24` so the generated documentation looks consistent. No code behavior changes.

This is a routine GitHub Actions CI maintenance change. It swaps the weekly automated code-formatting job from using a floating nightly Rust toolchain to a custom project tool called cargo-rbmt, which pins the compiler version. There is no user-facing code change and no security-relevant behavior.

This commit is purely a housekeeping change to the project's continuous integration (CI) setup. It moves the files that record the library's public API surface from a shared top-level directory into each individual crate's own directory, and switches the CI workflow to use a different command to check those API files. There is no change to the actual Bitcoin library code that users run, and no security impact.

This commit is purely a cleanup of developer tooling. It removes old references to a pinned nightly Rust toolchain version from the pre-commit git hook and the justfile (a task runner). The actual toolchain version pins were already moved to the project's main Cargo.toml file in a previous change. There is no change to the library code, no change to how the software behaves for users, and no security relevance.

This commit only updates a version identifier for an internal CI/testing tool (rbmt). There are no code changes to the rust-bitcoin library itself, and nothing in the commit suggests any security issue.

This is a one-line change to the project's GitHub Actions CI workflow. It adds an explicit git reference (the previous commit SHA) when running pre-release checks, so the check can run correctly after a pull request is merged into the master branch. There is no change to the Rust library code, no security fix, and no vulnerability.

This commit is a routine code reorganization. It moves the definition of a parsing error type into a new 'error' submodule while keeping the same public name available at the top level. There is no security-relevant change.

This commit is purely a code formatting cleanup. It only reorders an import statement, removes extra blank lines, and reformats an array literal to fit style guidelines. There are no functional changes to the SHA-256 hashing code.

This commit only adds `#[rustfmt::skip]` annotations to three places in a SHA-256 cryptographic implementation file. These annotations tell Rust's automatic code formatter to leave those blocks alone. There is no change to program logic, constants, memory handling, or any behavior that could affect security.

This commit is a pure code reorganization: it moves existing error type definitions from several source files into a new dedicated `error` submodule and re-exports them at the crate root. There are no functional changes to how data is encoded or decoded, no bug fixes, and no security-relevant behavior changes.

This commit only updates the crate-level documentation in the consensus_encoding module. It expands the list of free-standing encoding and decoding functions with brief descriptions. No code behavior was changed.

This commit only adds documentation examples to two Rust macros. It does not change any executable code, logic, or security behavior. There is no security issue here.

This commit removes one blank line from a documentation comment in a Rust source file. It is purely a code-style cleanup with no functional or security relevance.