rust-bitcoin

This commit fixes a spelling mistake in two documentation files, changing 'sciptcode' to 'scriptcode'. It does not change any code, program behavior, or security properties.

This commit only updates a generated text file that lists the public API surface of the crate. It renames a handful of method entries from `min_bytes_needed` to `read_limit` in the API listing. There is no actual source code change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit is a simple rename of a Rust trait method from `min_bytes_needed` to `read_limit` across the codebase, along with an update to its documentation to clarify that it represents an upper bound on bytes that can be safely read. There are no logic changes, no bug fixes, and no security implications.

This is a minor code-quality change. A constant used only in tests that require the 'alloc' feature was not itself behind that feature gate, causing a compiler warning (Clippy lint) when building without that feature. The patch adds the missing feature gate so the constant is only compiled when needed. There is no security impact.

This commit is a routine code-quality fix. It adds Rust feature gates so that certain test-only structs and imports are only compiled when the 'alloc' feature is enabled, silencing a Clippy warning about structs that are never constructed. There is no security relevance.

This is a routine maintenance change to a fuzz-testing file. It removes two deprecated test helper functions from a list so that an automated daily fuzzing job stops failing. There is no change to production code, no user-facing behavior, and no security fix.

This commit is a routine internal cleanup. It replaces deprecated function names with their newer equivalents in two helper methods that calculate Bitcoin transaction weight. The actual math and behavior remain the same, and the old functions are still kept (just marked as deprecated). There is no security issue here.

This commit only adds documentation comments describing situations where certain functions could panic due to arithmetic overflow. No code behavior was changed, so this is a documentation-only update with no security impact.

This commit only adds a new automated test. It does not change any production code, fix a bug, or alter behavior. The test checks that when a Bitcoin address has an invalid payload length, the error message reports the actual decoded payload size (22 bytes) rather than the length of the base58-encoded string. There is no security issue in this change itself.

This commit only cleans up Rust code style by replacing explicit lifetime names with a shorthand. It does not change what the code does, how it handles data, or any security behavior. There is no security issue here.

This is a minor code cleanup in a benchmark file. A Rust linting tool (Clippy) complained that the benchmark was passing a meaningless empty value to a function. The developer changed the code to silence the lint. It does not affect real users, security behavior, or runtime code.

This is a small internal code cleanup in a Rust Bitcoin library. It removes a redundant boolean flag and instead uses the presence or absence of an optional decoder object to track the same state. The commit message and diff show no change in behavior, input handling, or output results.

This commit simply removes a convenience function (`with_length_prefix`) from an internal byte-slice encoder in a work-in-progress Rust Bitcoin consensus-encoding module. Users are told to compose an explicit length-prefix encoder manually instead. There is no bug fix, no security patch, and no indication this change addresses any vulnerability.

This is a small internal code cleanup in the rust-bitcoin library. It changes how a Bitcoin script's byte length is recorded during serialization, making the length prefix explicit rather than hidden inside another helper. There is no indication this fixes a security bug; it appears to be a refactoring step before removing an old helper constructor.

This commit only changes a code comment to make it clearer which Bitcoin script opcodes are treated as data pushes versus regular opcodes. No actual code behavior was changed, so there is no security impact.

This commit removes an unnecessary internal re-export of a small helper macro. It is a code cleanup found by the Clippy linter and has no security relevance.

This commit fixes a typo in a documentation comment. The comment incorrectly referred to a different type (TxMerkleNode) when it should have referred to CompactTarget. There is no code behavior change and no security impact.

This commit only updates a mutation testing configuration file. It tells the mutation testing tool not to bother testing certain simple functions that are just type casts for performance reasons. There is no code change, no bug fix, and no security relevance.

This commit only updates a mutation-testing configuration file. It tells the automated mutation-testing tool not to alter two specific functions because those alterations would make tests run forever. It does not change any actual Bitcoin library code, fix a runtime bug, or address a security vulnerability.

This commit only changes a configuration file for mutation testing. It makes an existing test exclusion more specific so that future code additions are still tested. There is no change to the actual Bitcoin library code, no bug fix, and no security relevance.

This commit fixes a minor error-message bug. When a Bitcoin base58 address decoded to the wrong number of bytes, the error reported the length of the original string instead of the length of the decoded payload. The actual validation logic did not change; only the diagnostic detail is corrected.

This commit adds a new way to serialize Bitcoin blocks into bytes in the rust-bitcoin library. It is a routine feature addition that wires together existing serialization code for block headers and transactions. There is no indication of a security bug or fix.

This commit is a straightforward internal code cleanup. It replaces a custom hand-written encoding helper for Bitcoin transaction witness data with a reusable, already-existing encoder component. There is no indication of a bug fix or security change.

This commit simply makes a previously internal helper type called CompactSizeEncoder available for public use. It is a one-line export change with no functional code modifications, no bug fixes, and no security implications visible in the diff.

This commit adds a new helper for writing Bitcoin-style compact-size numbers. It is a straightforward feature addition with no visible security bug. There is no indication it fixes a vulnerability or introduces a dangerous behavior.