Re-export locktime encoders and decoders
What changed, and why it matters
This commit simply makes a few existing locktime-related type names available through an additional public module path. It is a routine API consistency fix with no security relevance.
No security action needed; treat as a normal API consistency patch.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change adds re-exports of LockTimeEncoder, LockTimeDecoder, and LockTimeDecoderError from units::locktime::absolute into bitcoin::blockdata::locktime::absolute. No logic, encoding, decoding, or validation behavior is modified; only the public import surface is expanded to match the crate’s usual re-export pattern.
Changed components
bitcoin/src/blockdata/mod.rs public re-exportsInspect captured patch +5 / −3
diff --git a/bitcoin/src/blockdata/mod.rs b/bitcoin/src/blockdata/mod.rs
index 526189ed..5d531ecf 100644
--- a/bitcoin/src/blockdata/mod.rs
+++ b/bitcoin/src/blockdata/mod.rs
@@ -44,11 +44,13 @@ pub mod locktime {
// Re-export everything from the `units::locktime::absolute` module.
#[rustfmt::skip] // Keep public re-exports separate.
#[doc(inline)]
- pub use units::locktime::absolute::{error, Height, LockTime, MedianTimePast};
+ pub use units::locktime::absolute::{
+ error, Height, LockTime, LockTimeDecoder, LockTimeEncoder, MedianTimePast
+ };
#[doc(no_inline)]
pub use units::locktime::absolute::{
- ConversionError, IncompatibleHeightError, IncompatibleTimeError, ParseHeightError,
- ParseTimeError,
+ ConversionError, IncompatibleHeightError, IncompatibleTimeError, LockTimeDecoderError,
+ ParseHeightError, ParseTimeError,
};
#[deprecated(since = "TBD", note = "use `MedianTimePast` instead")]
Why this scored 16/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.