From 1cc6c60e28ce761428b443e696190a5dd757a1e8 Mon Sep 17 00:00:00 2001 From: trustkim Date: Fri, 9 Feb 2018 18:11:58 +0900 Subject: [PATCH] correct CLTV's note description I think CLTV is output-level locktime. so it should be corrected --- ch07.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch07.asciidoc b/ch07.asciidoc index a7bcbe48..f3bf4d53 100644 --- a/ch07.asciidoc +++ b/ch07.asciidoc @@ -325,7 +325,7 @@ More precisely, +CHECKLOCKTIMEVERIFY+ fails and halts execution, marking the tra [NOTE] ==== -+CLTV+ and +nLocktime+ use the same format to describe timelocks, either a block height or the time elapsed in seconds since Unix epoch. Critically, when used together, the format of +nLocktime+ must match that of +CLTV+ in the inputs—they must both reference either block height or time in seconds. ++CLTV+ and +nLocktime+ use the same format to describe timelocks, either a block height or the time elapsed in seconds since Unix epoch. Critically, when used together, the format of +nLocktime+ must match that of +CLTV+ in the outputs—they must both reference either block height or time in seconds. ==== After execution, if +CLTV+ is satisfied, the time parameter that preceded it remains as the top item on the stack and may need to be dropped, with +DROP+, for correct execution of subsequent script opcodes. You will often see +CHECKLOCKTIMEVERIFY+ followed by +DROP+ in scripts for this reason.