rust-bitcoin

This commit is a large API refactoring in the rust-bitcoin library. It removes the need for callers to pass an explicit secp256k1 cryptographic context object to many functions. Instead, the library now uses a global or internally-managed context. The change touches examples, tests, and core modules for addresses, BIP32 key derivation, scripts, PSBT signing, message signing, and Taproot. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a usability and maintainability improvement.

This commit updates the rust-bitcoin library to use a new beta version of its underlying secp256k1 cryptographic library (0.32.0-beta.2). It is a routine dependency upgrade that adjusts many internal calls to match the new library's simpler API. There is no direct evidence in the commit that this fixes a known security vulnerability, but it does remove an old, separately-patched version of a hashing dependency and moves to a newer cryptographic release. The main risk is that any upgrade of core crypto code could introduce subtle bugs or break downstream users who rely on the old API.

This commit changes a Bitcoin script number-reading function so it returns a 32-bit integer instead of a 64-bit one, and adds a separate function for reading the larger 5-byte numbers used by the CHECKLOCKTIMEVERIFY opcode. The change makes the API more accurately reflect what the code actually allows, and reduces the risk that callers accidentally treat a 5-byte value as a normal script number. It appears to be a defensive correctness fix rather than a response to an active exploit.

This commit fixes a denial-of-service weakness in how the library reads length-prefixed byte and element lists from untrusted data. Previously, the library would reserve up to 4 million bytes or elements immediately after seeing a length number, even if the actual data never arrived. Now it reserves memory in 1 MB chunks only as data actually comes in, so an attacker must send data to make the program use memory. The commit message and code comments explicitly describe this as a DoS-prevention change.

This commit only adds a new fuzz test for the 'units' crate. It does not change any production code, fix a bug, or alter behavior. There is no security issue introduced or patched here.

This commit adds a missing decoder for Bitcoin blocks in the rust-bitcoin library. It is a routine feature addition that lets the library read block bytes back into a Block object, complementing the already-existing encoder. There is no indication of a security bug being fixed.

This commit reduces how much memory is pre-allocated when reading a variable-length list of items from a Bitcoin peer message. Previously the code could reserve up to roughly a quarter of a block's worth of elements based on an untrusted length value, which could let a malicious peer trick the program into reserving a large chunk of RAM. The new code caps the initial reservation to at most 8,000 bytes and lets the vector grow normally if more items actually arrive. It is a hardening change, not a fix for a known active attack.

This commit reduces the initial memory allocation when decoding a variable-length list (Vec) from Bitcoin protocol data. Previously, the code could reserve a large chunk of memory based on an untrusted length value, which could be abused to waste or exhaust memory. The new code caps the initial reservation to roughly 8,000 bytes worth of elements and grows the vector only as items are actually read. This is a hardening change against denial-of-service via maliciously large length fields.

This commit simply renames a Rust internal field from `marker` to `_marker` in one struct. It is a pure code-style cleanup with no functional, security, or API change.

This commit fixes a bug in how the rust-bitcoin library decodes Bitcoin transactions that have no inputs. Normally, the library uses a special encoding for zero-input transactions. The decoder was incorrectly trying to read witness data even when there were no inputs, which would cause decoding to fail. The fix skips witness decoding when there are no inputs, and a new test verifies that an empty transaction can be encoded and decoded correctly.

This commit is a straightforward internal code cleanup. It removes a temporary 36-byte buffer and manual byte copying when decoding an OutPoint (a Bitcoin transaction reference), replacing it with a direct split of the already-decoded byte array. There is no security-relevant change.

This commit creates a brand-new, empty placeholder Rust crate named `bitcoin-crypto` inside the rust-bitcoin workspace. It contains no executable code, no cryptographic logic, and no changes to existing crates. The sole purpose is to reserve the package name on crates.io before someone else takes it. There is nothing here that could affect security.

This commit is a routine API cleanup. It adds missing public re-exports of types from the underlying `primitives` and `units` crates into the main `bitcoin` crate, and adjusts documentation attributes so the exports display correctly. There is no change to behavior, logic, or security-sensitive code.

This commit adds a new development script and a corresponding CI step that automatically checks whether the `bitcoin` crate correctly re-exports public items from the `bitcoin_primitives` crate. It is purely a testing/quality-assurance change and does not modify any library code, user-facing behavior, or security-sensitive logic.

This commit simply renames a test-generation script and updates the GitHub Actions workflow that calls it. The old file `contrib/generate-re-export-test.sh` is renamed to `contrib/generate-primitives-re-export-test.sh`, and the CI step name and command are updated accordingly. The script's contents are unchanged. There is no security relevance.

This commit only adds new test code and a development-only dependency. It does not change any production code, fix a bug, or alter behavior. There is no security issue here.

This commit adds a new public helper type, EncodableByteIter, that lets callers read the serialized bytes of any Encodable object one byte at a time. It is a pure feature addition with no bug fixes, no changes to existing behavior, and no security-relevant content in the commit message or diff.

This commit only adds a new documentation file describing which versions of the rust-bitcoin library are considered long-term support (LTS) and which dependency versions correspond to each release. No code was changed, and there is no security fix or vulnerability present.

This commit is a routine maintenance patch that updates example code and tests to match a newer version of the underlying secp256k1 cryptography library. It replaces deprecated random-number calls with their modern equivalents and switches to a renamed key-construction function. There is no indication of a security vulnerability being fixed.

This commit only adds explicit version numbers to internal Rust package dependencies in a configuration file (Cargo.toml). It makes no code changes and does not fix or introduce any security issue. It is a routine release-preparation change.

This commit simply removes a few sentences from the project's README that told developers they could run the CI pipeline locally using a tool called 'act'. It is a documentation-only change with no code modifications and no security relevance.

This commit only changes a documentation comment for an internal Rust macro. It removes an outdated note claiming the macro checks for an 'alloc' feature and updates the description to match what the code actually does. No code behavior changes, and there is no security relevance.

This commit only adds two documentation files. One asks automated coding tools (AI agents) to identify themselves in commit messages, and the other is a one-line pointer to that file. There is no code change, no bug fix, and no security impact.

This commit updates the underlying cryptographic library (rust-secp256k1) from version 0.30.0 to 0.31.1 and makes the small code changes needed to keep the project compiling. The newer library version may include its own bug fixes, but the commit itself is a routine dependency upgrade rather than a direct fix for a known security flaw in rust-bitcoin.

This commit removes a single empty example file named 'ecdsa-psbt' from the rust-bitcoin repository. The file contained only a blank line and had no executable code, so the change cannot affect software behavior or introduce any security issue.