What changed, and why it matters
This commit only fixes a spelling mistake in documentation comments. The word 'OP_CHEKCLOCKTIMEVERIFY' is corrected to 'OP_CHECKLOCKTIMEVERIFY' in three places. There are no code behavior changes, no security fixes, and no functional impact.
No security action needed. Treat as a routine documentation cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a pure documentation typo correction within units/src/locktime/absolute/mod.rs. It changes three occurrences of the misspelled opcode name ‘OP_CHEKCLOCKTIMEVERIFY’ to the correct ‘OP_CHECKLOCKTIMEVERIFY’ inside doc comments and an inline comment. No executable code, logic, or API surface is modified.
Changed components
units/src/locktime/absolute/mod.rs (documentation comments only)Inspect captured patch +3 / −3
diff --git a/units/src/locktime/absolute/mod.rs b/units/src/locktime/absolute/mod.rs
index ed0a3a28..ca24454a 100644
--- a/units/src/locktime/absolute/mod.rs
+++ b/units/src/locktime/absolute/mod.rs
@@ -156,7 +156,7 @@ impl LockTime {
Ok(Self::from_consensus(lock_time))
}
- /// Constructs a new `LockTime` from an `nLockTime` value or the argument to `OP_CHEKCLOCKTIMEVERIFY`.
+ /// Constructs a new `LockTime` from an `nLockTime` value or the argument to `OP_CHECKLOCKTIMEVERIFY`.
///
/// # Examples
///
@@ -264,7 +264,7 @@ impl LockTime {
/// If `self` is a blockheight based lock then it is checked against `height` and if `self` is a
/// blocktime based lock it is checked against `time`.
///
- /// A 'timelock constraint' refers to the `n` from `n OP_CHEKCLOCKTIMEVERIFY`, this constraint
+ /// A 'timelock constraint' refers to the `n` from `n OP_CHECKLOCKTIMEVERIFY`, this constraint
/// is satisfied if a transaction with `nLockTime` set to `height`/`time` is valid.
///
/// If `height` and `mtp` represent the current chain tip then a transaction with this
@@ -283,7 +283,7 @@ impl LockTime {
/// fn get_height() -> absolute::Height { todo!("return the current block height") }
/// fn get_time() -> absolute::MedianTimePast { todo!("return the current block MTP") }
///
- /// let n = absolute::LockTime::from_consensus(741521); // `n OP_CHEKCLOCKTIMEVERIFY`.
+ /// let n = absolute::LockTime::from_consensus(741521); // `n OP_CHECKLOCKTIMEVERIFY`.
/// if n.is_satisfied_by(get_height(), get_time()) {
/// // Can create and mine a transaction that satisfies the OP_CLTV timelock constraint.
/// }
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.