rust-bitcoin

This is a tiny, non-security change in test-only code. It swaps one standard-library import for an equivalent core-library import so that a verification tool (Kani) can run in environments without the full standard library. There is no change to actual wallet or transaction logic, and no user-facing behavior changes.

This commit only adds a new regression test. It does not change any production code. The test checks that a function called from_base64 correctly rejects base64 inputs that decode to fewer or more than 65 bytes. Because no actual fix is included in this commit, the commit itself does not introduce or remove a security vulnerability; it merely adds a test to help catch the bug in the future.

This commit fixes a bug in the rust-bitcoin library where a specific function used to verify Bitcoin signed messages could crash the program. The crash could be triggered by feeding it a carefully crafted 88-character base64 string that decoded to 66 bytes instead of the expected 65 bytes. The fix adds proper length checks so the function returns a clean error instead of panicking, and also rejects 64-byte results that were previously silently accepted.

This commit fixes a bug where a Bitcoin data decoder could silently ignore parts of incoming data. The decoder only processed each chunk of data once, but some decoders don't finish a chunk in one go. Leftover bytes were effectively dropped, which could cause malformed or incomplete data to be accepted as valid. The fix repeatedly feeds the remaining bytes until the chunk is fully consumed or an error occurs.

This commit only adds a regression test for a previously existing bug in a decoding helper. It does not change any production code, so by itself it cannot introduce a security vulnerability. The test documents a bug where a decoder could lose unconsumed bytes under specific conditions, but the actual fix must have happened in an earlier commit not shown here.

This commit only adds a new regression test for an already-fixed bug in a Rust Bitcoin IO decoding function. It does not change any production code, so by itself it cannot introduce or fix a security vulnerability. The test documents a subtle edge case where a decoder consumes input one byte at a time.

This commit fixes a one-unit boundary error in how rust-bitcoin decides whether a time-based transaction lock has expired. The code previously treated 'lock time equal to median time past' as satisfied, but Bitcoin's BIP-113 rule requires strict less-than. A transaction built with rust-bitcoin using an equal-time lock could be accepted locally but then rejected by Bitcoin Core, causing inconsistent behavior, failed broadcasts, or mempool rejection.

This commit only updates generated text files that list the public API surface of the `bitcoin_internals` crate. The removed lines describe a simple helper trait (`ToU64`) and its implementations for unsigned integer types. There is no code change, no bug fix, and no security relevance visible in the diff.

This commit is a simple internal code reorganization. It moves a small helper trait called ToU64 from one internal crate (internals) into the main bitcoin crate, and updates import statements accordingly. There is no change to what the code does, no bug fix, and no security-relevant behavior change.

This is a small internal cleanup change in the rust-bitcoin library's peer-to-peer networking code. It replaces one use of a helper trait called ToU64 with a direct Rust built-in conversion (u64::from). The behavior is identical because a u32 value always fits safely into a u64. There is no security issue here.

This commit fixes a bug in a Rust Bitcoin library function that reads and decodes data. Previously, when reading data in chunks, the code would pass a chunk to the decoder once and then discard any leftover bytes the decoder did not fully consume. This could cause incomplete decoding, corrupted results, or unexpected failures when processing Bitcoin data streams. The fix repeatedly feeds the same chunk to the decoder until it is fully consumed.

This commit fixes a bug where displaying a specific error message in Bitcoin address parsing could cause the program to crash with a stack overflow. The crash only happens in 'no_std' builds (a special configuration without the standard library). The fix replaces an incorrect macro with the correct one so the error message is shown without trying to endlessly include itself as its own source.

This commit simply removes an unused import statement from a test module. It does not change any program logic, data handling, or security behavior. There is no security relevance.

This is a routine automated update that changes one line in the project's configuration file, bumping the pinned Rust nightly compiler version from April 2026 to June 2026. There is no code change, no bug fix, and no security-related content in the commit.

This commit only cleans up test code by removing unnecessary '&' symbols inside format!() calls. It does not change any runtime behavior or fix a security issue.

This is a minor code cleanup in the rust-bitcoin library. A developer replaced a verbose match block with the shorter `?` operator, which does the exact same thing in Rust: if an error occurs, return it immediately; otherwise continue. There is no functional change and no security impact.

This commit fixes a typo in an error message displayed to users. The message 'hex string is contains prefix' was corrected to 'hex string contains prefix'. It has no security relevance.

This commit is a one-line documentation fix inside a non-public Rust macro. It corrects the description of a macro parameter from 'err' to 'inner' so the internal comments match the actual code. There is no code behavior change, no security fix, and no user-facing effect.

This commit only removes two redundant sentences from Rust documentation comments. It does not change any executable code, logic, or behavior. There is no security impact.

This commit only fixes wording in code comments/documentation. It changes descriptions of three functions so the docs accurately describe what the functions do. No actual code behavior was changed, so there is no security impact.

This commit only fixes typos, grammar, punctuation, and formatting in documentation comments and one code example. There are no code logic changes, no API changes, and no behavior changes. It is purely a documentation quality cleanup.

This commit is a routine code reorganization: it moves many Bitcoin script opcode constants from the main `bitcoin` crate into a lower-level `primitives` crate, then re-exports them so existing users still see the same names and values. There is no change to what the opcodes mean or how they behave, and no security fix or vulnerability is described.

This commit only updates generated text files that list the public API surface of the rust-bitcoin 'primitives' crate. It records that the opcodes module and its constants are now publicly exposed. There are no code changes, no bug fixes, and no security-related modifications.

This commit adds a harmless convenience conversion that lets an Opcode be turned into a u8 number, matching the existing conversion from u8 to Opcode. It also adds a test to confirm the conversions work both ways. There is no security issue here.

This commit simply moves the definition of the Opcode type from one internal module to another and re-exports it so existing code keeps working. It is a routine code reorganization with no functional or security changes.