rust-bitcoin

This commit fixes two spelling mistakes in code comments and documentation links. One corrects a grammatical phrase about Bitcoin block version bits, and the other fixes a typo in a hyperlink label pointing to Bitcoin Core's source code. There are no code behavior changes.

This is a small change to an internal maintenance script used to generate dependency lock files for testing. It adds the '--all-features' flag so that optional features are included when checking the project against minimal and recent dependency versions. The commit message explicitly says this is currently a no-op because rust-bitcoin has very few optional dependencies. There is no indication this fixes a security vulnerability.

This commit is a routine build-maintenance change. It tightens how the project tests against the oldest allowed versions of its dependencies, and refreshes a checked-in lock file so those oldest versions are actually used in CI. There is no product bug fix, no change to the library code users run, and no security issue being patched.

This commit only updates the minimum required versions of development and optional third-party dependencies (like serde, arbitrary, arrayvec, and serde_json) across workspace Cargo.toml files and the minimal lockfile. It does not change any application code, cryptographic logic, or network handling. The stated purpose is to make the project's automated minimum-version checks work reliably with newer Cargo tooling, not to fix a security vulnerability.

This commit only adds a documentation policy guideline about how to format hyperlink references in Rust source-code comments. It does not change any executable code, cryptographic logic, network handling, or APIs.

This commit only adds and edits project planning documentation (markdown files about crate organization, roadmap, coding policy, keys/crypto, and Taproot). No source code, build scripts, tests, or dependencies were changed. There is no security-relevant behavior introduced or fixed.

This commit only renames a documentation file from docs/address.md to docs/addresses.md and updates the matching link in the roadmap. No code, logic, or security behavior changed.

This commit simply swaps one internal test-only helper crate for another. It changes how test code converts hex strings into byte arrays, with no effect on the actual library users run in production. There is no security issue here.

This commit removes the Coveralls code-coverage reporting workflow from the repository. It deletes the GitHub Actions file that ran test coverage on every push and pull request, and updates the workflow list in the README. There is no change to the actual Bitcoin library code, its tests, or its security behavior.

This commit fixes a build-configuration bug in the `io` crate of rust-bitcoin. The `io` crate uses a macro from another internal crate (`internals`) whose generated code depends on an `alloc` feature, but `io` was not forwarding the `alloc` feature to `internals`. This could cause compilation failures or missing functionality when `io` is used without the default `std` feature but with `alloc`. It is a correctness and reliability fix rather than a direct exploitable vulnerability.

This commit is a pure documentation and comment cleanup. It changes how Bitcoin Improvement Proposal (BIP) numbers are written throughout the codebase from inconsistent styles like 'BIP32', 'BIP 341', and 'BIP-32' to a uniform 'BIP-XXXX' format with four digits and a hyphen. No program logic, code behavior, or security properties were changed.

This commit removes a convenience conversion that let developers accidentally treat a Taproot transaction digest as an ECDSA-style message. It is a defensive API cleanup: it makes the library's types more precise so users cannot pass a Taproot sighash through an ECDSA-specific wrapper. There is no direct bug being fixed, but the change prevents a class of future misuse where a Taproot signature could be computed over a wrongly-wrapped hash.

This commit is a routine automated code-formatting run using the nightly version of rustfmt. It only changes whitespace, line breaks, import order, and comment alignment across 19 files. No program logic, security behavior, or API semantics were altered.

This commit corrects a spelling mistake in a documentation file, changing the heading 'Depenency tree' to 'Dependency tree' in the README. It does not change any code or affect how the software runs.

This commit fixes two typos/grammar mistakes in plain-text documentation comments describing Bitcoin script opcodes. The actual code behavior is unchanged; only the human-readable descriptions were corrected.

This commit simply updates the version of the Rust nightly compiler used by the project's automated GitHub CI testing from one weekly nightly build to the next. It changes only one line in a configuration file and has no effect on the actual Bitcoin library code that users run.

This commit simply bumps the version number of a CI linting tool (cargo-semver-checks) used in GitHub Actions from 0.42.0 to 0.43.0. It does not change any library code, runtime behavior, or user-facing functionality. There is no security relevance visible in the commit.

This commit fixes a panic (crash) in two Bitcoin weight-unit conversion helpers when they are called on the maximum possible weight value. The functions now use saturating addition, so instead of overflowing and crashing they return a large but valid rounded-up result. This is a reliability fix that prevents denial-of-service-style crashes from untrusted inputs.

This is a tiny code-quality change that replaces a hardcoded number (4) with a named constant already defined in the same file. It does not change behavior, fix a bug, or address any security issue.

This commit adds a new automated fuzz test for the Weight type in the rust-bitcoin library. Fuzz tests feed random or semi-random inputs to code to find crashes or unexpected behavior. There is no change to production code, no bug fix, and no security patch in this commit.

This commit updates a single version number in a shell script that auto-generates GitHub Actions workflow files. It changes the referenced GitHub action 'actions/download-artifact' from version 4 to version 5 so newly generated workflows match a version already bumped elsewhere by an automated tool. There is no code change affecting the Rust Bitcoin library, its users, or any runtime behavior.

This commit is a documentation and deprecation cleanup for Taproot-related witness methods in the rust-bitcoin library. It rewrites misleading doc comments, deprecates the `tapscript` method in favor of `taproot_leaf_script`, and clarifies that callers should validate the output script (not the returned script) when checking for Taproot or Segwit v0 spends. There is no code behavior change beyond adding a Rust deprecation attribute.

This commit fixes a spelling mistake in a comment inside a shell script used for checking API changes. It changes 'effected' to 'affected' with no functional code changes.

This commit simply moves the project's coding-style policy guide from CONTRIBUTING.md into a new docs/policy.md file. It is a documentation reorganization with no code changes, no functional changes, and no security relevance.

This is a routine API refactor in a Rust Bitcoin library. It introduces a new public type called Ntxid to represent a 'normalized transaction ID' instead of returning a generic hash. The goal is to let the library stabilize one of its core modules without forcing users to depend on another internal module. There is no security bug being fixed here.