rust-bitcoin

This commit adds new Rust traits (interface definitions) for a streaming, push-based Bitcoin consensus decoder. It only introduces abstract code patterns—no actual decoding logic for real Bitcoin data types, no changes to existing behavior, and no bug fixes. There is nothing here that directly affects security.

This commit is a routine dependency version bump in a build configuration file. It changes the required version of an optional test/fuzzing helper library from '1.4' to '1.4.1' so that it matches another crate in the same workspace and resolves a Cargo lock-file conflict. There is no indication this fixes or introduces a security vulnerability.

This is a routine automated update by Dependabot that bumps the GitHub Actions 'actions/checkout' dependency from version 4 to version 5 in the project's CI workflow file. There is no indication of a security fix or vulnerability in the commit itself.

This is a large internal refactoring of the rust-bitcoin library. It moves Bitcoin hash wrapper types (like transaction IDs and block hashes) into a new private module so that the lower-level `hashes` crate no longer appears directly in the public API. The visible behavior of the library is intended to stay the same. There is no obvious security vulnerability introduced, but any wide-reaching refactor carries a small risk of accidental behavioral changes in serialization or parsing.

This commit is an automated code-formatting run by rustfmt. It only changes whitespace, line breaks, and the order of some module declarations and import lists. No program logic, algorithms, or security behavior were changed.

This commit fixes a simple typo in a documentation comment ('the the' → 'the'). It changes no executable code, no APIs, and no behavior. There is no security relevance.

This commit fixes a typo in a test-only panic error message. The message previously referenced a function name that did not exist; it now references the correct function name. There is no change to runtime code, no security fix, and no user-facing behavior change.

This commit only adds documentation comments explaining that two Rust Bitcoin types can panic if someone tries to create a script larger than about 2 billion bytes. No code behavior was changed, so it does not fix or introduce a security vulnerability by itself.

This commit is a routine test and fuzzing infrastructure update. It adds new ways to automatically generate random P2P message objects for fuzz testing, moves existing fuzz targets into a dedicated 'p2p' directory, and renames them. There is no change to production behavior, no bug fix, and no security patch in the code that runs in real Bitcoin applications.

This commit updates version numbers inside a script that automatically generates fuzz-testing configuration files. It does not change any actual library code, cryptographic logic, or user-facing behavior. It simply keeps the generated files in sync with dependency versions that were already updated elsewhere in the project.

This commit only adds new automated tests for how the OutPoint data type is serialized and deserialized. It does not change any production code, fix a bug, or introduce a security issue. It is a routine test-only change.

This commit rewrites how the OutPoint type (a Bitcoin transaction reference made of a transaction ID and output index) is serialized and deserialized with the serde library. It replaces a macro with hand-written code. The change is described by the author as a code cleanup to remove an ugly macro, not as a security fix. There is no direct evidence in the commit or supplied references that this fixes a vulnerability.

This commit adds new serialization (encoding) helpers for several Bitcoin unit types—Amount, BlockHeight, LockTime, and Sequence—so they can be written to the wire in the standard Bitcoin format. It is a straightforward feature addition with no visible bug fix or security change.

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 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 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 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 is a one-word typo fix in the project's public planning document (roadmap.md), changing 'stabalize' to 'stabilize'. It does not modify any code, build configuration, tests, or documentation that affects how the software works. There is no security relevance.

This commit is a simple rename of an internal Rust module from `parse` to `parse_int`. It does not change what the code does, only how it is named and where it appears in the public API. There is no security fix or behavior change.

This commit fixes a subtle arithmetic bug in how Bitcoin fee rates and transaction weights are rounded up. The previous code tried to avoid crashes on extremely large numbers by using 'saturating addition,' but that produced slightly wrong rounded-up results for the maximum possible values. The patch replaces that workaround with Rust's proper div_ceil function, which gives the mathematically correct ceiling division even at the extremes. In practice, this mostly affects edge-case calculations with maximum values and is unlikely to be directly exploitable for theft, but it removes a source of incorrect fee/weight estimates.

This commit is a routine maintenance change that raises the Minimum Supported Rust Version (MSRV) from Rust 1.63.0 to 1.74.0 across documentation, CI configuration, and package manifests. It does not change any code logic, cryptographic operations, or security behavior. It simply tells users and automated tooling that the project now requires a newer Rust compiler.

This commit only adds a new unit test to the rust-bitcoin library. It does not change any production code. The test checks that the library can still serialize and deserialize very large Bitcoin transactions, witnesses, and script signatures. There is no bug fix or security patch here.

This commit only fixes a spelling mistake in the changelog ('paramater' to 'parameter') and adds a missing newline at the end of the file. It changes no code, no build files, and no documentation that affects how the software works. There is no security relevance.

This commit is a trivial typo fix: it renames a local variable from 'delimeter' to 'delimiter' with no functional change. The code behavior is identical before and after.