rust-bitcoin

This commit simply reorganizes project documentation. It moves contributor and maintainer instructions from the main README file into the CONTRIBUTING guide, and adds a short section about no-std support to the README. No program code was changed, so this cannot affect security.

This commit only updates the project's README file to add and reorganize links to release notes (CHANGELOG files) for several software components. It does not change any program code, build scripts, tests, or documentation that affects how the software behaves.

This commit is a routine code-maintenance change. It moves lint (style and warning) rules from an individual package configuration file into shared workspace-level rules, and swaps one allowed style warning for another. There is no change to program logic, no bug fix, and no security relevance.

This commit simply renames a pre-release version label from 'alpha.0' to 'beta.0' in package metadata and lock files. It makes no code changes and has no security relevance.

This commit only edits the project's changelog file. It documents an upcoming beta release and lists previously merged changes, but it does not modify any source code, build scripts, tests, or configuration. There is no security-relevant code change to review.

This commit fixes a bug in the Rust Bitcoin library's script builder. When building a Bitcoin script, after pushing a number onto the stack, the builder would incorrectly remember the last opcode it had seen. This caused a later call to `push_verify()` to try to combine with that remembered opcode, producing an invalid or unexpected script. The fix clears that remembered state whenever an integer is pushed, and adds a test to prevent regression.

This commit removes a helper function called all_targets_satisfied() from the peer-to-peer (p2p) message handling code. That function used to check whether every block header in a 'headers' message met its own proof-of-work target. The change is framed by the author as a design cleanup: p2p should only encode and decode network messages, while proof-of-work verification should be done by the caller or elsewhere. Removing the check does not by itself create a vulnerability, but any downstream code that relied on this function to validate headers before processing them will no longer get that protection automatically. Those callers must now add the check themselves or use a different validation path.

This commit is a housekeeping change that moves shared code-quality rules from individual package configuration files into a single workspace-wide configuration. It does not change any program logic, fix a bug, or alter how the software behaves at runtime. One package also adds a warning to discourage risky indexing patterns, which is a preventive code-quality measure, not a security patch.

This commit is a routine code reorganization: it moves two related data types, FilterHash and FilterHeader, from the main bitcoin crate into the p2p crate because they are used in peer-to-peer network messages. It also removes one test assertion that checked a now-removed helper method. There is no security fix or vulnerability here.

This commit is a routine release-tracking change. It bumps the version number of the `bitcoin-primitives` crate from `1.0.0-rc.0` to `1.0.0-rc.1` in lock files and dependency manifests, and replaces placeholder "TBD" strings in deprecation notices with actual version numbers. There are no functional code changes and no security implications.

This is a routine code cleanup in an example file. A developer replaced one function call with another that does the same thing, because the old function name is being retired. There is no security issue here.

This is a one-line change in a test file that swaps a deprecated type name for its newer replacement. It has no security relevance: it does not alter production code, cryptographic logic, parsing, network handling, or any behavior visible to users of the library.

This commit changes version constraints for several in-development (release candidate) internal dependencies so Cargo will use an exact version rather than automatically picking a newer release candidate. It is a build/maintenance change to prevent unexpected dependency resolution, not a fix for a security vulnerability.

This commit creates a brand-new, empty placeholder crate named `bitcoin-bip158` inside the rust-bitcoin workspace. It adds no executable code, no network functionality, no cryptographic operations, and no changes to existing crates. It is purely a project-structure refactor in preparation for later moving BIP-158 filter code out of the main `bitcoin` crate.

This commit adds a small, public helper function to create a new type of Bitcoin address called 'pay-to-anchor' (P2A). It is a pure feature addition with no visible bug fix or security-related change. There is no indication of a vulnerability being patched.

This is a routine release-tracking commit. It bumps the version number of the `bitcoin-units` crate from `1.0.0-rc.2` to `1.0.0-rc.3`, updates other crates in the same project to depend on the new version, refreshes lock files, and adds a changelog note that a recent pull request now allows underscores as separators in `Amount` values (for example, writing 1_000_000 instead of 1000000). There are no code changes in this commit itself.

This commit only fills in placeholder version numbers in deprecation warnings. It does not change any program behavior, fix any bug, or introduce any security issue. It is a routine documentation/metadata cleanup.

This commit changes a single version requirement in a Rust package file so that a pre-release dependency is pinned to an exact version rather than allowing newer release-candidate versions. It is a build-stability fix, not a security patch. There is no code change that fixes a vulnerability or changes runtime behavior.

This is a routine code cleanup inside test code only. It swaps deprecated function calls for newer, non-deprecated equivalents in a Rust unit test file. There is no change to production behavior, no bug fix, and no security relevance visible in the commit.

This commit is a routine cleanup that swaps deprecated type names for their newer replacements in test files only. It does not change any production code, behavior, or security properties.

This commit only adds a missing changelog entry for a previously released version of an internal Rust library. It documents two routine maintenance items: raising the minimum supported Rust version and adding a dependency. There is no code change and no security relevance.

This commit is a routine version bump for an internal helper crate. It only changes version numbers in package files and a changelog entry. There is no code change, no bug fix, and no security issue visible in the diff.

This commit is a code-quality cleanup, not a security fix. It adds a `let _ = w[15];` line in two SHA hashing implementation files solely to silence a new Rust clippy lint about an unused assignment inside a macro on the final round of SHA-256 and SHA-512. The generated machine code and behavior are unchanged.

This commit adds a single annotation telling the Rust linter (clippy) to ignore a 'function is too long' warning on an internal helper function. It does not change any executable code, behavior, or data handling. There is no security relevance.

This commit adds convenience Rust traits (+= and -= operators) for a wrapper type called NumOpResult. It does not fix a bug or change existing behavior; it only makes it easier to add or subtract values that are already wrapped in a NumOpResult. There is no security relevance in the change itself.