rust-bitcoin

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 a spelling mistake in documentation comments. The word 'OP_CHEKCLOCKTIMEVERIFY' is corrected to 'OP_CHECKLOCKTIMEVERIFY' in three places. There are no code behavior changes, no security fixes, and no functional impact.

This commit only rewrites the abbreviation 'iff' (meaning 'if and only if') to its full phrase in four documentation/comments files. No code logic, APIs, or behavior changed. There is no security relevance.

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 fixes a broken documentation hyperlink. The comment that describes a Bitcoin improvement proposal (BIP 68) was accidentally pointing to the wrong BIP page (BIP 65). No program code, logic, or security behavior was changed.

This commit only adds new unit tests for an existing Sum implementation. It does not change any production code, fix a bug, or introduce new functionality. 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 pins the version of a CI tool (cargo-public-api) used to check whether the project's public programming interface has changed. It is a build-maintenance change to prevent unexpected CI failures when the tool releases new versions requiring newer Rust compilers. There is no security issue in the code change itself.

This commit only reorganizes where module declarations appear in four Rust source files. It groups private modules together and public modules together, with no changes to what code is exposed, how it behaves, or any security-sensitive logic. There is no security issue here.

This commit simply reorders two blocks of code in a single Rust source file. It moves an `extern crate test;` statement to sit with other `extern crate` statements, and moves a `mod benches;` module declaration below it. The commit message explicitly states this is an internal-only change with no logic change, and the diff confirms no executable code was altered.

This commit refactors how Rust Bitcoin serializes and deserializes lists of data. It replaces a macro that generated separate code for each supported type with a single generic implementation that uses Rust's runtime type identification to treat Vec<u8> specially. The change is mostly a code cleanup, but it introduces unsafe pointer casts and transmutes that rely on the runtime TypeId check being correct. If that check were bypassed or misunderstood, it could lead to incorrect serialization or memory safety issues.

This commit only changes Clippy lint configuration in two Cargo.toml files. It removes a no-longer-existing lint setting and, in one crate, swaps it for a stricter but unrelated lint. There is no change to actual Bitcoin logic, no bug fix, and no security relevance.

This commit is a routine maintenance change. It updates the Rust nightly compiler version used by the project and adds a single annotation to silence a Clippy lint warning inside a const-conditional macro. There is no functional code change and no security relevance.

This commit adds a single comment line inside documentation example code to silence a Clippy lint about an unused import. It is purely a code-quality/documentation change and has no security relevance.

This commit simply bumps the version number used by the project's automated GitHub testing from Rust compiler version 1.88.0 to 1.89.0. It changes one line in a CI configuration file and has no effect on the actual Bitcoin library code that users run.

This commit only updates the project's mutation-testing configuration file. It tells the mutation-testing tool to skip testing certain deprecated functions. There is no change to actual library code, no bug fix, and no security relevance.

This commit fixes a typo in a code comment, changing 'Porallel' to 'Parallel'. It does not change any executable code, logic, or behavior. There is no security impact.

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 only adds a documentation comment to the top of a Rust source file. It explains that the `primitives` crate's types are re-exported in the main `bitcoin` crate, so users do not need to import `primitives` directly. There are no code changes, no bug fixes, and no security implications.

This commit only changes documentation wording in source code comments, replacing the word 'Creates' with 'Constructs' across 13 files to match the project's style policy. No program logic, behavior, or security properties were modified.

This commit only adds a blank line in a package configuration file to visually separate optional dependencies from required ones. There is no code change, no behavior change, and no security relevance.

This commit is a purely stylistic cleanup inside the rust-bitcoin library. It changes how internal helper macros are referenced from a two-level path like `crate::internal_macros::macro_name!` to a single-level path like `internal_macros::macro_name!` after importing the module once. The commit message explicitly says this is for readability only and does not change any behavior or fix any security issue.