rust-bitcoin

This commit only adds new unit tests for the Sequence type. It does not change any production code, fix bugs, or alter behavior. There is no security relevance.

This commit removes a documentation-only Rust compiler feature flag (`doc_auto_cfg`) from the BIP-158 crate. It does not change any executable code, runtime behavior, or security-sensitive logic. The change only affects how documentation is generated on docs.rs and appears to be a cleanup because the feature was unstable or causing issues.

This commit simply makes an existing internal crate called `primitives` usable directly through the main `bitcoin` crate (e.g., `use bitcoin::primitives`). It is a routine API/export convenience change with no security relevance visible in the code.

This commit only updates the project's mutation-testing configuration file. It tells the mutation-testing tool to skip two more deprecated functions when looking for untested code changes. There is no change to the actual Bitcoin library code, no bug fix, and no security relevance.

This commit only adds a new unit test that checks whether a Witness object's reported byte size matches the length of its actual encoded bytes. It does not change any production code, fix any bug, or alter behavior. There is no security relevance.

This change is a routine internal dependency cleanup. The developers moved some shared type definitions (like block and transaction identifiers) from a large crate called `bitcoin` into a smaller, more focused crate called `bitcoin-primitives`. This reduces duplicate dependencies for downstream projects but does not change what the code does or fix any security problem.

This commit removes an unused wildcard import in a test module. It is a minor code cleanup with no security relevance.

This commit is purely a code-formatting cleanup. It runs the project's formatter across 58 files, adjusting whitespace, line breaks, import order, and adding two missing semicolons the formatter exposed. There are no functional code changes, no bug fixes, and no security-relevant alterations.

This commit only adds documentation comments to two Rust source files. It does not change any executable code, so it cannot introduce or fix a security vulnerability by itself. The comments explain an existing behavior of the push_slice() function regarding how small numeric values are encoded in Bitcoin scripts.

This commit fixes how the library builds Bitcoin script instructions when pushing a single zero byte (0x00) onto the stack. Previously, ScriptBuf::push_slice() emitted an invalid opcode (OP_PUSHBYTES_0, which does not exist in Bitcoin) for a 0x00 byte, while Builder::push_slice() had its own separate logic that already handled 0x00 correctly by falling through to a normal non-minimal push. The patch makes Builder delegate to ScriptBuf so both behave the same way, and changes ScriptBuf to emit a valid push instruction for 0x00. A script containing the invalid opcode would be rejected by the Bitcoin network, so this is a correctness/security bug in transaction/script construction.

This commit only updates test code. It removes an 'ignore' marker from a test and corrects the expected byte output for pushing a single zero byte onto a Bitcoin script. There is no change to production code and no security issue.

This commit fixes a bug in the rust-bitcoin library where calling a function to push the single byte 0x00 onto a Bitcoin script would incorrectly push an empty byte array instead. In Bitcoin scripts, pushing the number 0 (empty) and pushing the byte 0x00 are semantically different operations. The fix ensures 0x00 is pushed as a one-byte data push, while the number 0 remains represented as an empty push (OP_0).

This commit only adds new automated tests for an existing data type called BlockTime. It does not change any production code, fix bugs, or alter behavior. There is no security issue here.

This is a tiny test-only cleanup commit. It removes an unused trait import and replaces a helper constructor with direct struct field assignment in a unit test. There is no security relevance.

This is a routine Rust API improvement that lets two small data types be copied implicitly instead of requiring an explicit clone. It does not fix a security bug and does not introduce an obvious vulnerability.

This commit removes a third-party dependency called `arrayvec` from the `bitcoin-primitives` crate and rewrites how a Bitcoin block header is printed as text. The old code built the text in a small fixed-size buffer from `arrayvec`; the new code streams the bytes directly through an internal formatting helper. There is no security fix here—this is a routine dependency-reduction refactor.

This commit adds text files that record the current public API of the 'bitcoin_internals' crate and updates a shell script to include that crate in routine API-change checks. It does not change any source code, behavior, or fix any bug. It is purely a documentation/CI tracking change.

This commit simply removes an internal helper function that was no longer used. It is a routine cleanup change with no security relevance.

This commit replaces the custom code that reads Bitcoin transaction witness data with a shared decoding library. The change is described by the author as a temporary, slightly messy refactor to keep an older decoding helper working while a newer encoding crate takes over. There is no claim in the commit that this fixes a security bug, and the diff itself is mostly code removal and plumbing a new error variant. It could affect how malformed witness data is rejected, but no vulnerability is disclosed or demonstrated.

This commit only updates documentation. It expands a design document explaining how a new consensus encoding crate works and removes a TODO comment from another document. No code, tests, build files, or configuration were changed, so it cannot introduce or fix a security vulnerability.

This is a tiny documentation-only change in an embedded-systems example README. It corrects the documented heap size from 524288 to 262144 and removes an outdated line about a secp256k1 buffer size. No code was changed, so there is no security impact.

This is a routine automated update to the project's GitHub CI configuration, changing the pinned stable Rust compiler version from 1.91.1 to 1.92.0. It does not modify any source code, dependencies, or runtime behavior of the rust-bitcoin library. There is no security relevance in this change.

This commit only reorders two Rust attribute lines on test functions so that #[test] appears above #[cfg(...)]. It is a cosmetic/style change with no effect on what code runs or how it behaves. There is no security relevance.

This commit simply renames a local variable from 'rinsed' to 'roundtrip' in several test files. It is a cosmetic code cleanup with no functional changes and no security relevance.

This commit only removes documentation sections from README files in multiple Rust packages. It deletes redundant mentions of the minimum Rust version and licensing information, which are already present in the package manifest files. There are no code changes, no functional changes, and no security implications.