rust-bitcoin

This commit is a routine internal code reorganization. It moves some methods of the Network type into a new 'extension trait' called NetworkExt so that the underlying Network type can be shared with a separate crate. There is no security bug being fixed here.

This commit only changes documentation comments (docstrings) for several constants in the proof-of-work module. It rewords descriptions to be consistent and adds a source reference comment. No code behavior is altered, so there is no security impact.

This commit only adds a documentation link inside a code comment. It does not change any executable code, behavior, or security properties of the library.

This commit is a routine code-quality refactor in the rust-bitcoin library. It wraps the underlying secp256k1 keypair type in a library-specific type so that parsing errors can be more precise and the public API is cleaner. There is no direct security vulnerability being fixed here; it is an interface improvement that may indirectly reduce misuse.

This commit is a routine code refactoring in the rust-bitcoin library. It splits the existing difficulty calculation functions into two parts: new lower-level functions that take a maximum target directly, and the original functions that now simply call these new functions with the network's maximum target from the Params object. There is no change to the actual math or behavior, and no security issue is present.

This commit is purely a code-formatting cleanup performed by an automated rustfmt nightly run. It reorders imports, collapses or expands brace blocks, removes blank lines, and adjusts line wrapping in test code. No program logic, APIs, or security behavior was changed.

This commit changes how the Rust Bitcoin library allocates memory when decoding a Bitcoin transaction's witness data. Previously, the decoder could double its internal buffer repeatedly, which could let a maliciously crafted transaction force the program to reserve far more memory than needed. The new code allocates memory in roughly 1 MB batches instead. A test was added that feeds a 4,000,000-element witness and checks that the decoder only allocates about 16–17.5 MB, suggesting the change is meant to limit memory blow-up during decoding.

This commit only adds a new unit test. It does not change any production code. The test checks that the library rejects Bitcoin transactions containing an output worth more than the maximum allowed money (MAX_MONEY + 1 satoshi) when decoding transaction bytes. It is a defensive test borrowed from Bitcoin Core's test data, confirming an existing safety check works.

This commit adds a safety check in the rust-bitcoin library so that when a Bitcoin transaction is being decoded, the total value of all its outputs is rejected if it exceeds the protocol's maximum allowed money supply (MAX_MONEY). This prevents a class of bugs similar to the historic Bitcoin Core overflow issue referenced as CVE-2010-5139, where an impossibly large total output value could cause incorrect accounting or consensus problems.

This commit adds two new helper functions, flush_to_vec and flush_to_writer, to the consensus_encoding crate. They let developers take an already-created Encoder object and write its contents out to a Vec or an I/O writer. The existing encode_to_vec and encode_to_writer functions are refactored to use these new helpers internally. There is no security fix or behavior change; it is a straightforward API convenience addition.

This commit is a routine cleanup of the public API surface. It stops two internal helper types (BlockTimeDecoder and BlockTimeDecoderError) from being exported at the top level of the primitives crate. The types are still available inside the crate where they are actually used. There is no security fix here and no indication of a vulnerability.

This is a routine internal code reorganization. The project is moving the definition of Bitcoin network types (like Mainnet and Testnet) from one internal crate to another newly created crate. There are no user-facing behavior changes and no security fixes.

This commit removes a small helper method called Magic::from_params from the rust-bitcoin peer-to-peer networking crate. The method was redundant because the same conversion can already be done through Rust's standard TryFrom trait. There is no security issue here; it is a routine code cleanup to simplify the public API and remove an unnecessary dependency on the Params type.

This commit is purely cosmetic: it moves one optional dependency line down by one position in a configuration file so that optional and non-optional dependencies are grouped separately, matching project convention. There is no code change and no security relevance.

This commit only adds new unit tests for error types in the Bitcoin block primitives. It does not change any production code, fix bugs, or alter behavior. There is no security issue here.

This commit adds a new automated test to verify that a helper function correctly returns nothing when given a non-coinbase Bitcoin transaction. It does not change any production code, fix a bug, or alter behavior. It is purely a test addition.

This commit only adds new unit tests for encoding and decoding the block version number. It does not change any production code, so it cannot introduce or fix a security vulnerability on its own.

This commit only updates documentation comments for two existing Rust functions, adding details about what errors they can return. No code logic was changed, so it cannot introduce or fix a security vulnerability on its own.

This commit only fixes compiler lint warnings. It adds missing feature gates so that test code compiles cleanly when certain optional features are enabled or disabled. There is no change to runtime behavior, no bug fix, and no security relevance.

This change only touches an example program used for documentation and CI demos. It makes the seed argument optional by providing a documented default value. There is no security issue: the seed was already hard-coded in the comment above, and the example is not production code.

This commit only adds two new automated tests that check how many bytes a Block and Header decoder expects to read. It does not change any production code, fix a bug, or alter behavior. There is no security issue here.

This commit is a minor code cleanup in test code only. It replaces verbose match statements with the shorter matches! macro in two unit tests. The change does not affect production code, behavior, or security.

This commit only adds an extra test case to an existing unit test. It does not change any production code, so it cannot introduce or fix a security vulnerability by itself. The new assertion checks that a block with an invalid witness commitment is rejected by the validation function, which is a normal correctness test rather than a security patch.

This commit simply deletes five old benchmark test files that were accidentally left behind after benchmarks were moved to a newer testing framework. It removes unused code and has no effect on the actual Bitcoin hashing library or its users.

This commit adds standard encoding and decoding support for a Bitcoin peer-to-peer network message called CFHeaders (compact filter headers). It is a routine implementation of serialization traits and does not appear to fix or introduce any security issue.