rust-bitcoin

This commit is an automated code-formatting run by rustfmt. It only reorders an import statement and removes a trailing space in a test line. There is no functional change to the program.

This is a routine automated update that changes one line in the project's configuration file, bumping the pinned Rust nightly compiler version from March 27, 2026 to April 10, 2026. There is no code change, no bug fix, and no security-relevant content.

This commit changes only a fuzz-testing helper shell script. It adds a configuration entry telling an internal lint tool (rbmt) that the crate 'hex-conservative' is allowed to appear as a duplicate dependency in the fuzz workspace. There is no change to production code, no cryptographic logic, no network handling, and no user-facing behavior. It is not a security fix and does not introduce a security issue.

This commit adds a new automated fuzz-testing target for Partially Signed Bitcoin Transactions (PSBTs) in the rust-bitcoin project. It does not change production behavior, fix a bug, or alter any user-facing API. It only adds test infrastructure and small helper implementations needed to generate random PSBT-like objects for fuzzing. The fuzz target itself even documents a pre-existing known panic condition it works around, rather than fixing it.

This commit adds a GitHub Actions workflow that automatically opens or closes a repository issue when two specific scheduled CI workflows (Fuzz and Kani CI) fail or succeed on the master branch. It is purely an automation/notification change and does not modify any library code, cryptography, network handling, or user-facing behavior of the rust-bitcoin crate.

This commit only adds #[inline] hints to small, simple functions in the rust-bitcoin units crate. It is a performance-oriented code-quality change with no functional or security impact.

This commit only updates generated API snapshot text files in the rust-bitcoin repository. These files list what functions and types are publicly exposed by the library, but they are not source code. The deletions show that some internal helper types and a debug function are no longer part of the public API, which is a normal cleanup or refactoring outcome. There is no code change, no bug fix, and no security issue visible in this commit.

This commit only hides two internal helper items from the public API documentation. It does not change any code behavior, access permissions, or security boundaries. There is no security issue here.

This commit simply hides an internal data structure (called State) from outside users of the library. It is an API-cleanup change, not a security fix. There is no patch for a vulnerability and no indication of any exploit or unsafe behavior.

This commit only updates the text of an automated comment left by a GitHub workflow when an API-breaking change is detected. It changes the instructions so they point to the correct CI job name. There is no code change, no security fix, and no vulnerability.

This commit is a pure code reorganization: it moves error type definitions from the main message module into a new 'error' submodule and re-exports them so existing code keeps working. There are no functional changes to how messages are parsed, validated, or handled.

This commit is a routine code reorganization. It moves several error type definitions from the main p2p crate file into a new dedicated error submodule, then re-exports them so existing code can still use them the same way. There is no functional change to how the library behaves.

This commit is a pure code reorganization: it moves several error type definitions from the main message_blockdata module into a new error submodule and re-exports them. There are no functional changes to how errors are created, handled, or displayed, and no security behavior changes.

This commit is a straightforward internal code reorganization in the rust-bitcoin library. It moves several error type definitions from the main address module into a new error submodule and re-exports them so existing users are unaffected. There is no change to how addresses are parsed, validated, or handled, and no security fix or vulnerability is present.

This commit is a pure code reorganization: it moves several error type definitions from the main message_filter file into a new error submodule and re-exports them. There are no functional changes to how the code behaves, no bug fixes, and no security improvements or regressions.

This commit is a pure code reorganization: it moves several error type definitions from the main message_network.rs file into a new error submodule and re-exports them. There is no change to how the code behaves, no bug fix, and no security-relevant change.

This commit is a simple internal code cleanup in the rust-bitcoin library. It moves an error type for compact block network messages into its own submodule and re-exports it. There is no change to how the code behaves, no bug fix, and no security-relevant change.

This commit is a straightforward internal code reorganization. It moves three error type definitions for bloom filter network messages into a new 'error' submodule and re-exports them. There is no functional change to how the code behaves, no bug fix, and no security-relevant change.

This commit is a straightforward internal code reorganization. It moves three error types (MerkleBlockDecoderError, PartialMerkleTreeDecoderError, and MerkleBlockError) from the main merkle_tree module into a new error submodule and re-exports them. There is no change to how the code behaves, no bug fix, and no security improvement or regression.

This commit is a pure code reorganization: it moves several error type definitions from the main BIP-152 compact blocks module into a new `error` submodule and re-exports them. There are no functional changes to how errors are created, handled, or reported. It is a refactoring change aimed at making the codebase structure more consistent and documentation more uniform.

This commit is a small internal refactoring in the peer-to-peer networking code. It swaps a generic encoder helper macro for an exact-size version so callers can ask 'how many bytes will this produce?' without actually encoding anything. There is no indication this fixes a bug, let alone a security vulnerability.

This commit adds a small performance and convenience feature to a Bitcoin peer-to-peer networking library written in Rust. It lets callers ask up front how many bytes an address encoding will produce, without actually doing the encoding. There is no security bug being fixed here; it is a routine enhancement with new tests.

This commit adds new Rust conversion helpers (From trait implementations) that let callers pass secret key types by reference instead of by value. It is a routine ergonomic/API improvement and does not change security behavior. The existing logic for deriving public keys from secret keys is unchanged; only the way callers provide the input is made more convenient.

This commit narrows the visibility of two internal accessor methods from public to crate-internal. It is a routine API-cleanup change with no security relevance: it does not fix a bug, change behavior, or address any reported vulnerability.

This commit is a routine ergonomic/API change in the rust-bitcoin library. It changes several key-conversion functions so they accept references instead of taking ownership of private key and keypair values. There is no security bug being fixed and no new vulnerability being introduced; it simply makes the API easier to use after the underlying secret key types stopped being implicitly copyable.