AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 20 Bitcoin

Merge rust-bitcoin/rust-bitcoin#6730: primitives: Remove `BlockHashDecoder` from `transaction` module

Public commit record

What the developer wrote

Authored by Andrew Poelstra

91/100 · Strong
Merge rust-bitcoin/rust-bitcoin#6730: primitives: Remove `BlockHashDecoder` from `transaction` module

76c19176514ef42d104ada21a1c47f58e762e7dd Update API files (Mitchell Bagot)
ff712f73840768fd2481d3a0b51890062049d36a primitives: Remove BlockHashDecoder from transaction module (Mitchell Bagot)

Pull request description:

The BlockHash type is present in the primitives::block module. However, the decoder and its associated error type is re-exported in both the transaction and block modules.

Remove BlockHashDecoder and BlockHashDecoderError re-exports from the primitives::transaction module.


ACKs for top commit:
tcharding:
ACK 76c19176514ef42d104ada21a1c47f58e762e7dd
apoelstra:
ACK 76c19176514ef42d104ada21a1c47f58e762e7dd; successfully ran local tests


Tree-SHA512: daf983550fea7219b6c8f9adcb3c96b5d7dd4c9eebead23b3bba97b8e27fb93965d5f37b7ee624744fbf0618f8570ffbc69c9ae1063ad9f971cd2d454ecc5144
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This change is a routine cleanup of the library's public API. It removes two items (BlockHashDecoder and BlockHashDecoderError) that were accidentally re-exported from the wrong module. The actual decoder and error type still exist in the correct block module, so no functionality is removed. There is no security issue here.

Recommended action

No security action needed. Treat as a normal API-breaking cleanup; downstream users importing these types from the transaction module will need to update their imports to the block module.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 20/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 5/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.