rust-bitcoin

This commit is a routine code cleanup, not a security fix. It removes some text-formatting features from the Bitcoin opcode type and replaces them with a simpler automatically-generated debug format. The change is driven by Rust language rules (orphan rules) that prevent adding certain traits once a type moves to another crate. Existing string output remains available through Opcode::as_str().

This commit simply deletes a test file that checked how Bitcoin script opcodes were serialized to JSON. The underlying serialization feature for opcodes had already been removed in a previous change, so this test was no longer useful. There is no code change that affects how the library behaves, and no security issue is introduced or fixed here.

This commit is a routine internal code reorganization. It moves the implementation of a function that returns the human-readable name of a Bitcoin script opcode from one place in the source file to another. The public behavior of the library does not change, and there is no security relevance.

This is a straightforward internal code cleanup. The change replaces direct access to a private field (`Opcode.code`) with calls to an existing public method (`to_u8()`). The behavior of the code is identical; it is purely a refactoring step to keep a field private while still allowing the same logic to work.

This commit is a routine internal refactoring in the rust-bitcoin library. It makes an internal module visible at the crate level (but not to end users) so that a future change can move a data type into it. It does not change any behavior, fix a bug, or alter security logic.

This commit is a routine internal code reorganization. It moves three helper methods (classify, decode_pushnum, as_str) off the main Opcode type into a new 'extension trait' called OpcodeExt. The actual behavior of those methods is unchanged; only how callers access them is different. There is no security fix or vulnerability here.

This is a routine internal code cleanup in the Rust Bitcoin library. It adds a new public constant function `Opcode::from_u8` so that Bitcoin script opcodes can be created from raw byte values inside constant contexts (for example, at compile time). The existing `From<u8>` conversion is rewritten to use this new function. There is no security-relevant change: the behavior is identical, no new data is accepted, and no existing checks are removed.

This commit removes unused hex-decoding helper code from an internal module. It is a cleanup change: it deletes functions and an error type that are no longer used anywhere in the project. There is no indication this fixes a security bug or changes behavior visible to users.

This commit only updates an automatically-generated text file that lists the project's public API surface. It removes entries for some error types that were renamed or replaced elsewhere, and updates type signatures to match. No actual source code, logic, or behavior changed in this commit, so it has no security relevance on its own.

This commit is a routine internal cleanup in the rust-bitcoin library. It removes a duplicate way of turning hex strings into Bitcoin data structures (blocks, block headers, transactions) and replaces it with a single shared helper called decode_from_hex. The actual hex decoding logic stays functionally the same; only the error types and code paths are simplified. There is no indication this fixes a security bug.

This commit is a routine internal cleanup in the rust-bitcoin library. It removes a custom error type and switches one function to use a newer, shared hex-decoding path. There is no indication this fixes a security bug; it is a refactoring change.

This commit is a routine version bump for the bitcoin-units crate from 0.4.0 to 0.5.0. It updates dependency references and lock files, and records in the changelog that some deprecated and internal-only hex-parsing helper functions were removed. There is no security-relevant code change in the diff itself.

This commit only updates generated API text files that list what functions are publicly available in the library. It removes lines that described four internal 'unchecked' hex-parsing helper functions from the public API snapshot. There is no actual code change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit removes a helper function from the public API of a Rust Bitcoin library. The function was never intended for outside use and only parses hex numbers that have no '0x' prefix. Making it private reduces the library's exposed surface, which is a good defensive practice, but there is no evidence it fixed an active security bug.

This is a tiny code cleanup inside test code. It moves a variable assignment to a slightly different spot so the test reads more logically. There is no change to how the program behaves, no security fix, and no user-facing effect.

This commit is an automated code-formatting run by rustfmt. It only reorders import/use statements in two files without changing any program logic, behavior, or security properties.

This commit only adds compiler hints (#[inline]) to small functions in the crypto module. It does not change any behavior, logic, or data handling. There is no security issue here.

This commit removes unused helper code that converted the impossible-to-create Infallible error type into several private inner error types. These inner types are not exposed to users of the library, and the removed conversions served no internal purpose. There is no security-relevant change.

This is a small performance optimization in how Bitcoin witness data is decoded. It changes when memory is reserved during decoding to avoid one extra memory reallocation for large witness elements. There is no security bug being fixed and no indication this change is security-relevant.

This commit only updates a mutation-testing configuration file. It tells the mutation-testing tool to skip certain artificial code changes in a WitnessDecoder because those changes only affect memory capacity reservations and cannot be detected by tests. There is no change to actual library code, no bug fix, and no security relevance.

This commit only adds new performance benchmarks for decoding Bitcoin transaction witness data. It does not change any production code, fix any bug, or alter program behavior. There is no security relevance.

This commit fixes a denial-of-service (DoS) weakness in how the rust-bitcoin library decodes Bitcoin transaction witness data. Previously, an attacker could send only about 10 bytes of data and trick the decoder into reserving 16 MB of memory up front. The new code only allocates memory for bytes that have actually arrived, making memory-exhaustion attacks much harder. The commit also simplifies the code and removes several helper functions and constants.

This commit is a routine version bump for the bitcoin-network-kind crate from version 0.1.0 to 1.0.0. It updates version numbers in package manifests, lock files, and a changelog, but does not change any source code or behavior. There is no security relevance.

This commit only updates generated text files that list the public API surface of the crate. The change records that a new standard Rust conversion trait (`From<Infallible>`) is now implemented for an existing error type. No source code, logic, or behavior was changed, so there is no security issue here.

This is a routine Rust language addition: it lets the library's network-parsing error type be created from Rust's 'Infallible' type, which can never actually occur. It has no security relevance on its own.