From 0aa5e51b6b9f4652ea280c6beb9e3ecb8c42ff8b Mon Sep 17 00:00:00 2001 From: "judymcconville@roadrunner.com" Date: Mon, 1 May 2017 12:19:27 -0700 Subject: [PATCH] Edited ch07.asciidoc with Atlas code editor --- ch07.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch07.asciidoc b/ch07.asciidoc index fcdf5ea1..5653b1ed 100644 --- a/ch07.asciidoc +++ b/ch07.asciidoc @@ -316,7 +316,7 @@ BIP-68 and BIP-112 were activated in May 2016 as a soft-fork upgrade to the cons ==== Relative Timelock with nSequence -Relative timelocks can be set on each input of a transaction, by setting the +nSequence+ field in each input. +((("nSequence field")))((("scripting", "timeclocks", "relative timeclocks with nSequence")))Relative timelocks can be set on each input of a transaction, by setting the +nSequence+ field in each input. ===== Original meaning of nSequence @@ -347,7 +347,7 @@ The standard is defined in https://github.com/bitcoin/bips/blob/master/bip-0068. ==== Relative Timelocks with CHECKSEQUENCEVERIFY (CSV) -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. +((("scripting", "timelocks", "relative timeclocks with CHECKSEQUENCEVERIFY")))((("CHECKSEQUENCEVERIFY (CSV)")))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 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.