Merge pull request #236 from edposnak/ch07-CSV-fix

nSequence must be greater than or equal to the CSV parameter
7 years ago · 9d17fe0565
parent 41833a480c 5eda229055
commit 9d17fe0565
1 changed files with 1 additions and 1 deletions
--- a/ch07.asciidoc
+++ b/ch07.asciidoc
@ -354,7 +354,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.