From 5eda22905547b9386c5b2f347e93c4955ea24a7d Mon Sep 17 00:00:00 2001 From: Ed Posnak Date: Fri, 3 Feb 2017 12:17:30 -0500 Subject: [PATCH] nSequence must be greater than or equal to the CSV parameter for the required number of blocks or seconds have elapsed. --- ch07.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch07.asciidoc b/ch07.asciidoc index 195c52e5..284fecf1 100644 --- a/ch07.asciidoc +++ b/ch07.asciidoc @@ -356,7 +356,7 @@ BIP-68 Relative lock-time using consensus-enforced sequence numbers:: https://gi Just like CLTV and nLocktime, there is a script opcode for relative timelocks that leverages the nSequence value in scripts. That opcode is +CHECKSEQUENCEVERIFY+ commonly referred to as +CSV_ for short. -The CSV opcode when evaluated in a UTXO's redeem script, allows spending only in a transaction whose input nSequence value is lower than the CSV parameter. Essentially, this restricts spending the UTXO until a certain number of blocks or seconds have elapsed relative to the time the UTXO was mined. +The CSV opcode when evaluated in a UTXO's redeem script, allows spending only in a transaction whose input nSequence value is greater than or equal to the CSV parameter. Essentially, this restricts spending the UTXO until a certain number of blocks or seconds have elapsed relative to the time the UTXO was mined. As with CLTV, the value in CSV must match the format in the corresponding nSequence value. If CSV is specified in terms of blocks, then so must nSequence. If CSV is specified in terms of seconds, then so must nSequence.