rust-bitcoin

This commit only adds a new documentation file: an Architecture Decision Record (ADR) explaining the project's plan to create a dedicated 'consensus_encoding' crate. It contains no code changes, no bug fixes, and no security-related content. It is purely a planning/design document.

This commit adds a blank template document for Architecture Decision Records (ADRs). It is purely documentation and contains no code changes, no configuration changes, and no security-relevant content.

This commit is a minor code cleanup that removes unnecessary copy operations (clones) inside test code only. It does not change any production behavior and has no security relevance.

This commit only adds a new test case. It does not change any production code. The test checks that decoding a SegWit-formatted transaction with no witness data correctly produces an error. There is no fix or behavior change in the actual decoder.

This commit only adds a new test that encodes a Bitcoin transaction and decodes it again to make sure the result matches the original. It does not change any production code, fix a bug, or introduce a security issue. The commit message mentions a 'mutant in push_bytes,' which is testing jargon for a surviving fake code change during mutation testing, not a real vulnerability.

This commit only updates a configuration file used for mutation testing. It tells the mutation-testing tool to skip certain patterns that would otherwise cause test runs to hang. There is no change to the actual Bitcoin library code, no bug fix, and no security patch.

This commit only adds a new unit test for an existing function. It does not change any production code, so it cannot introduce or fix a security vulnerability by itself. The test verifies that witness data with a length of exactly 4,000,000 bytes is accepted, while a length of 4,000,001 bytes is rejected.

This commit only removes two short documentation comments from a Rust trait implementation. The actual code behavior is unchanged. There is no security relevance.

This commit only removes a documentation comment that duplicated a warning already present on the trait definition. No code behavior changed, and there is no security relevance.

This commit removes a single blank line between a Rust test attribute (#[test]) and the test function it decorates. It is a cosmetic/style-only change with no functional or security effect.

This commit only removes a documentation comment that duplicated an existing warning elsewhere in the code. No program logic, behavior, or security boundary changed.

This is a routine internal code reorganization. A helper function that feeds encoded data into a hash calculation was moved from one Rust crate to another, and the dependency direction between those two crates was reversed. The actual logic of the function did not change, and there is no indication this fixes or introduces a security bug.

This commit only changes a test comment. It removes two commented-out test lines and adds a brief explanatory note about an existing optimization. No code behavior was changed, and there is no security relevance.

A single number in the rust-bitcoin peer-to-peer networking code was corrected: the protocol version that advertises support for the BIP31 ping/pong feature was changed from 60000 to 60001. This is a bug fix that aligns the code with the Bitcoin protocol specification. The wrong value could cause a node to misidentify itself or misjudge peers during version negotiation, but it is not a direct theft-of-funds or remote-code-execution vulnerability.

This is an automated code-formatting commit from rustfmt. It only changes whitespace, line breaks, and brace style in two source files. No program logic, behavior, or security properties were changed.

This commit only adds new unit tests for encoding and decoding routines in the rust-bitcoin consensus_encoding crate. It does not change any production code, fix bugs, or alter behavior. The tests cover corner cases such as zero-length arrays, empty slices, boundary values for compact-size integers, and state transitions in combined encoders/decoders.

This commit is a routine release-preparation change. It bumps the version number of the `bitcoin-primitives` crate from 0.101.0 to 1.0.0-rc.0, updates two lockfiles, and adds a long changelog entry describing past improvements. No code behavior is changed, and there is no security fix or vulnerability introduced in the diff itself.

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 is a routine version bump for the bitcoin-units crate from 1.0.0-rc.1 to 1.0.0-rc.2, triggered by a dependency version change in bitcoin_hashes. It only updates version numbers in lock files and package manifests; no source code, logic, or behavior changed.

This commit simply makes an existing internal dependency (the `hashes` crate) publicly visible to users of the `consensus_encoding` crate. It is a routine API/export change with no security relevance visible in the code.

This commit is a routine version bump for a Rust package called `bitcoin-consensus-encoding`, moving it from one release candidate version to the next. It only updates version numbers in package files and lock files. There are no code changes, no bug fixes, and no security-related changes.

This commit is a routine packaging change for the rust-bitcoin library. It adds an explicit version number to an internal dependency so the crate can be published to the Rust package registry. There is no security issue in the change itself.

This commit is a routine release preparation: it bumps the version number of the `bitcoin_hashes` crate from 0.16.0 to 0.17.0, updates the changelog, and refreshes lock files and dependency version constraints in related crates. There are no code changes, bug fixes, or security-related modifications in the diff.

This commit removes a Rust compiler feature flag called doc_auto_cfg from 11 library files. The feature was removed in recent nightly Rust compilers and was causing documentation builds to fail when publishing crates. It is purely a build/documentation compatibility fix with no effect on the actual Bitcoin code or its security.

This commit is a routine developer-experience improvement. It moves the version of an internal helper repository (maintainer-tools) into a plain text file so both CI and the local justfile use the same version. It adds local recipes to run the same checks that run in CI. There is no change to the actual Bitcoin library code, no bug fix, and no security-related content.