rust-bitcoin

This commit fixes a one-word typo in an error message. The message previously said 'Ipv addresses' and now correctly says 'Ipv4 addresses'. It is purely a cosmetic/user-facing string correction with no functional or security effect.

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 is a one-line fix inside an internal Rust helper macro. The macro was accidentally reading from the original macro parameter `$a` instead of the local copy `a` when filling the output buffer. In Rust macros, this kind of mismatch can cause surprising compile-time or expansion errors, or in some edge cases allow the macro to behave differently than intended. The change makes the macro consistently use the local variable it already created, which is a correctness and maintainability improvement. There is no direct evidence in the commit that this was a security vulnerability or that it is exploitable.

This commit simply updates the version of the Rust nightly compiler used by the project's automated GitHub CI tests from one weekly release to the next. It changes one line in a configuration file and has no direct security relevance to the library code itself.

This commit removes a duplicate documentation comment that was accidentally placed above an import statement. It is a cosmetic cleanup with no functional code change and no security relevance.

This commit only reformats a documentation comment so it fits on one line instead of two. There is no code behavior change and no security relevance.

This commit is a purely cosmetic documentation and comment change. It rewrites Bitcoin Improvement Proposal (BIP) references from formats like 'BIP-32' or 'BIP 68' to a new standardized four-digit format like 'BIP-0032' or 'BIP-0068' across changelogs, examples, source code comments, and markdown docs. No program logic, code behavior, or security properties were changed.

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 adds two new helper functions to a Bitcoin library's encoding module: one that turns an object into a byte vector, and another that writes an object's bytes to a standard output destination. It also adds tests for these helpers. There is no indication of a security bug or fix in the code or commit message.

This is a small build-configuration fix in a Rust package file. It stops an optional dependency from automatically pulling in its default features, and explicitly wires the crate's own 'std' and 'alloc' features through to that dependency. The change is defensive: without it, a no-std build could accidentally end up requiring standard-library features, which can cause compilation failures or force an unwanted configuration. There is no direct evidence of an exploitable vulnerability.

This is a minor code cleanup that rewrites one function to use a more modern Rust helper method. It does not change what the function does or fix any security issue.

This commit only reformats documentation comments. It changes how web links to Bitcoin Improvement Proposals (BIPs) are written in source-code documentation, moving the actual URL to the bottom of the doc block rather than embedding it inline. No program logic, math, cryptography, or transaction handling code is modified.

This commit removes an accidentally enabled 'rand' feature from a cryptographic dependency. The project did not intend to require randomness support from the secp256k1 library in its default build. Having it enabled could have forced extra code and dependencies into builds that were supposed to be deterministic or minimal, and could have subtly changed which APIs are available. It is a cleanup/revert of a mistaken change, not a fix for an active exploit.

This is a tiny performance-only change inside test code. It swaps one way of creating a zero-filled vector for another equivalent but slightly faster method. It does not touch production code, user-facing behavior, or security logic.

This commit only fixes two small grammar mistakes in code comments/documentation. There are no code changes, no behavior changes, and no security implications.

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 simply deletes a one-character placeholder file named 'ex' that appears to have been accidentally added to the repository. It contains no code, no executable content, and no security-sensitive data.

This commit adds an optional 'arbitrary' feature to the p2p crate. It is a build/test tooling change that enables fuzz testing by exposing test-only arbitrary data generation. There is no runtime behavior change, no bug fix, and no security vulnerability introduced or patched.

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 corrects a spelling mistake in a documentation comment, changing 'vulerablles' to 'vulnerabilities'. It does not change any executable code or behavior.

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 commit fixes a logic bug in Bitcoin's BIP158 compact block filter code. Previously, if a user asked 'Is anything in this block relevant to me?' but provided an empty list of things to look for, the code incorrectly answered 'Yes, it matches.' This could make wallet or node software think every block was relevant, wasting resources, triggering unnecessary downloads, or causing denial-of-service-like behavior. The fix makes an empty query correctly return 'No match.'