fix: IsSatisfiedByTimeError::Incompatible wording to lock-by-time
What the developer wrote
Authored by yyhrnk
fix: IsSatisfiedByTimeError::Incompatible wording to lock-by-time
What changed, and why it matters
This commit fixes a typo in an error message. The message previously said 'lock-by-height' when it should have said 'lock-by-time'. It does not change any program logic, calculations, or security behavior.
No security action needed. Treat as a routine documentation/string-fix commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
A single-word change in the Display implementation for IsSatisfiedByTimeError::Incompatible in units/src/locktime/relative/error.rs. The error string is corrected from ‘lock-by-height’ to ‘lock-by-time’ to match the enum variant’s semantics. No code behavior, parsing, validation, or consensus logic is modified.
Changed components
units/src/locktime/relative/error.rsInspect captured patch +1 / −1
diff --git a/units/src/locktime/relative/error.rs b/units/src/locktime/relative/error.rs
index d24ebfeb..ec18483a 100644
--- a/units/src/locktime/relative/error.rs
+++ b/units/src/locktime/relative/error.rs
@@ -116,7 +116,7 @@ impl fmt::Display for IsSatisfiedByTimeError {
match *self {
E::Satisfaction(ref e) => write_err!(f, "satisfaction"; e),
E::Incompatible(blocks) =>
- write!(f, "tried to satisfy a lock-by-height locktime using blocks {}", blocks),
+ write!(f, "tried to satisfy a lock-by-time locktime using blocks {}", blocks),
}
}
}
Why this scored 15/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.