rust-bitcoin

This commit adds a new documentation file (docs/dependencies.md) describing the project's policy for deciding whether to add third-party dependencies. It contains no code changes, no configuration changes, and no security fixes. It is purely a policy/governance document pulled from an earlier team discussion.

This commit fixes two spelling mistakes in code comments and documentation links. One corrects a grammatical phrase about Bitcoin block version bits, and the other fixes a typo in a hyperlink label pointing to Bitcoin Core's source code. There are no code behavior changes.

This commit simply swaps one internal test-only helper crate for another. It changes how test code converts hex strings into byte arrays, with no effect on the actual library users run in production. There is no security issue here.

This commit corrects a spelling mistake in a documentation file, changing the heading 'Depenency tree' to 'Dependency tree' in the README. It does not change any code or affect how the software runs.

This is a routine API refactor in a Rust Bitcoin library. It introduces a new public type called Ntxid to represent a 'normalized transaction ID' instead of returning a generic hash. The goal is to let the library stabilize one of its core modules without forcing users to depend on another internal module. There is no security bug being fixed here.

This commit adds documentation showing the project's internal crate dependency tree and a helper command to regenerate it. It does not change any executable code, cryptographic logic, or network handling, so it has no security impact on its own.

This commit is a routine code cleanup that changes how internal Rust import statements are written. It replaces direct imports from internal sub-crates (like `units::BlockTime` or `primitives::Sequence`) with imports through the crate's own public re-exports (like `crate::BlockTime` or `crate::Sequence`). There is no change to program logic, behavior, or security.

This commit fixes three minor typos: one grammar correction in a code comment about SegWit transaction parsing, one grammar correction in a documentation comment about a feature flag, and one typo ('crate' to 'create') in an error message inside a test. There are no code behavior changes.

This commit is a simple renaming cleanup. It replaces the old term 'VarInt' with 'CompactSize' in comments, variable names, error variants, and test strings. No behavior of the code changes, and no security issue is introduced or fixed.

This commit only changes documentation comments in three source files. It replaces the word 'varint' with 'CompactSize' or 'length prefix' to match the project's current terminology. No code logic, serialization, or API behavior was altered.

This is a routine automated update by Dependabot that bumps a GitHub Actions helper (used to download build artifacts) from version 4 to version 5 in a daily fuzzing workflow. There is no indication of a security problem or malicious change in the commit itself.

This commit is a straightforward internal code reorganization. It moves a small helper type called CheckedData—used to bundle data with a 4-byte Bitcoin P2P checksum—from the main bitcoin crate into the p2p crate. The logic, behavior, and tests are copied almost unchanged. There is no security fix or vulnerability being patched.

This is a tiny test-only change that swaps one placeholder type for another in a single unit test. It does not alter any production code, behavior, or security boundary.

This commit only fixes three spelling mistakes in the project's CHANGELOG.md file ("serializaton" to "serialization", a duplicated "SimpleDecoder" to "SimpleEncoder", and "wrappend" to "wrapped"). It changes no source code, build scripts, tests, or documentation that affects how the software behaves. There is no security relevance.

This commit removes automatic serialization/deserialization support (via the serde library) for several core Bitcoin data types like Block, Transaction, and TxOut. It is a deliberate API cleanup, not a bug fix. The change could break downstream code that relied on these types being directly serde-serializable, but it does not introduce a memory-safety or cryptographic vulnerability on its own. The project notes that these types can still be serialized using Bitcoin consensus encoding instead.

This commit changes how two Rust Bitcoin library crates are configured during testing. It makes the code always use 'no_std' mode (a leaner environment without the standard library) even when running tests, and adjusts test imports to use allocator-provided collections instead of the standard library. It also replaces a 'HashSet' alias with a direct 'BTreeSet' import for clarity. There is no security-relevant change to runtime behavior or public API.

This commit fixes a spelling mistake in a code comment ('afformentioned' to 'aforementioned'). It does not change any executable code, data handling, or network behavior. There is no security relevance.

This commit fixes a typo in a code comment inside the p2p/src/lib.rs file. It changes 'instead' to 'instead' by adding a missing space after the closing backtick. There is no functional code change, no security impact, and no behavior change.

This commit is a routine code cleanup in the Rust Bitcoin library. It changes how internal helper macros are referenced, making their full module path explicit (e.g., `internal_macros::impl_consensus_encoding!` instead of importing and calling them directly). There is no change to program logic, data handling, or security behavior.

This commit fixes a typo in a comment within an example file. It changes 'Loop an retrieve new messages' to 'Loop and retrieve new messages'. There is no code behavior change and no security relevance.

This commit fixes a spelling mistake in a code comment, changing 'vulerabilities' to 'vulnerabilities'. No actual code behavior changed, so there is no security issue in the commit itself.

This commit is a routine cleanup of how Bitcoin amount-related error types are exposed to users of the Rust Bitcoin library. It moves error types into a dedicated `amount::error` submodule and adjusts re-exports so the public API is better organized. There is no indication this fixes a security vulnerability or changes how amounts are validated.

This commit is a routine library reorganization: it moves some error/result helper types into a newly public `result` submodule and removes their old re-exports from the crate root. There is no change to how calculations are performed, no bug fix, and no security-sensitive behavior is introduced.