rust-bitcoin

This commit adds the ability to serialize and deserialize a small fixed-capacity vector type (ArrayVec) used inside the rust-bitcoin library. It is a routine feature addition with explicit guards against overflowing the capacity during deserialization. There is no indication this fixes a security bug or introduces a vulnerability.

This commit only updates a generated text file listing the public API surface of the crate. It records that an internal ArrayVec type now implements standard serde serialization/deserialization traits. The diff itself contains no source code changes, no bug fixes, and no behavior changes.

This commit removes two PSBT (Partially Signed Bitcoin Transaction) fuzz testing targets from the project's automated fuzzing setup and adds a clarifying comment about why an explicit version number is needed for a local dependency. There is no change to the actual Bitcoin library code that users rely on, and nothing in the commit suggests a security vulnerability was fixed or introduced.

This commit adds a new helper function (constructor) to build a Bitcoin P2P network message header. It simply packages existing fields and computes the message checksum automatically. There is no indication it fixes a security bug or introduces a vulnerability; it appears to be a routine API improvement.

This commit only changes test code. It replaces byte-string literals with hex-string literals to make the test data easier to read and keep it consistent with other tests. The actual production code being tested is not modified, and the test behavior remains the same.

This commit removes old-style encoding implementations from three simple data types (ProtocolVersion, ServiceFlags, and Magic) in the rust-bitcoin peer-to-peer library. It is a routine code cleanup that switches these types to use a newer, dedicated encoding macro. There is no indication of a security bug being fixed.

This commit removes old-style encoding and decoding code for two Bitcoin peer-to-peer message types (MerkleBlock and PartialMerkleTree) and replaces it with a newer encoding system already present in the file. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine cleanup or migration to a newer serialization API.

This commit removes old, unused code that encoded and decoded Bitcoin peer network addresses using a legacy 'consensus' encoding system. It is a cleanup change: the deleted code appears to have been superseded by newer encoding machinery elsewhere in the crate. There is no indication in the commit that this fixes a security bug or that the removed code was reachable by attackers.

This commit removes old-style Bitcoin consensus encoding code from the peer-to-peer message filter module. It replaces hand-written encoding implementations with newer macro-generated ones that were already added elsewhere in the file. There is no indication in the commit that this fixes a security bug; it appears to be a routine cleanup/refactoring change.

This commit removes old-style encoding and decoding code for several Bitcoin peer-to-peer message types and replaces it with a newer, generated encoding system. There is no direct evidence in the commit or supplied references that this fixes a security vulnerability; it appears to be a routine refactoring or cleanup of legacy code.

This commit removes old, unused Bitcoin network message encoding code from the rust-bitcoin p2p library. It deletes fallback implementations that were kept alongside newer encoding logic. There is no direct evidence this fixes an active security bug, but removing redundant legacy code reduces the attack surface and the chance that outdated, potentially unsafe code paths could be accidentally used in the future.

This commit removes old, unused encoding code for Bitcoin peer-to-peer bloom filter messages. It is a cleanup change that deletes legacy implementations after newer replacement code was already in place. There is no indication this fixes a security bug or introduces a vulnerability.

This commit removes old-style serialization code for compact-block P2P messages and replaces it with a newer internal encoding system. It is a cleanup/refactoring change in the rust-bitcoin library. There is no direct evidence in the commit that it fixes a security vulnerability, but any encoding change can in principle affect how malformed network data is parsed.

This commit removes old-style Bitcoin P2P message encoding and decoding code from the rust-bitcoin library and replaces it with a newer encoding system. It is a cleanup/refactoring change, not a fix for an active security bug. The deleted code included checksum verification and message-length limits that now live in the new encoder, so the security of the library depends on whether the new code provides equivalent protections. The commit itself does not describe any security issue.

This commit is a routine API cleanup in the rust-bitcoin library. It changes several methods named to_public_key so they return a modern compressed public key type (FullPublicKey) instead of an older type that could be either compressed or uncompressed (LegacyPublicKey). The old behavior is preserved under new to_legacy_public_key methods. The change is about encouraging safer modern key handling, not about fixing an active security bug.

This commit only updates generated API text files to include a newly added public function, `drain_to_engine`, in the documented interface list. It does not change any source code, behavior, or security properties of the library. There is no security issue here.

This commit adds a new public helper function called drain_to_engine in the rust-bitcoin hashes crate. It simply refactors existing code so that the logic for feeding an encoder's output into a hash engine can be called independently. There is no indication of a bug fix or security issue in the commit message or diff.

This is a routine CI maintenance patch. A trait named Encodable was renamed to Encode elsewhere in the project, and this change updates a GitHub Actions workflow and a shell script so they reference the new name. It fixes a broken documentation-file path that was causing CI to fail. There is no security issue here.

This commit only adds a GitHub Actions step that frees disk space before running CI tests. It is a routine infrastructure/maintenance change with no user-facing or security-relevant code change.

This commit only changes the project's internal fuzzing test script. It adds a command-line option to control how long fuzzing runs, replacing a fixed 100,000-run limit with a default 100-second time limit. There is no change to the actual Bitcoin library code that users rely on, and no security issue is present.

This commit is a routine GitHub Actions maintenance change. It copies a small reusable workflow step (called 'setup-rbmt') from a separate repository into this one, so the project no longer has to reference an external repository version. There is no change to the actual Bitcoin library code, no user-facing behavior change, and no security fix or vulnerability introduced.

This commit only changes the list of feature combinations that are tested automatically in CI. It removes most of a large, exhaustive test matrix and keeps just two core combinations to avoid timeouts on older Rust compilers. There is no change to the actual library code, dependencies, or user-facing behavior.

This commit simply removes the nightly Rust toolchain from the project's automated test matrix. It is a routine CI cost-saving change and has no security relevance.

This commit adds a new continuous integration (CI) check and a helper script that make sure every type that can be encoded in the current version of the library is also tested by an existing differential fuzz test against an older version of the library. It does not change any library code, user-facing behavior, or fix a bug; it only strengthens automated testing.

This commit adds a new automated test (a fuzz target) that compares how the current development version of the rust-bitcoin library encodes Bitcoin data against the previous stable release (0.32). It does not change any production code, fix a bug, or introduce a vulnerability. It only adds testing infrastructure and dependency lockfile updates needed to run that test.