From d90861478786d1efaf53a1f0c5f2bb5dc907d356 Mon Sep 17 00:00:00 2001 From: nadams Date: Mon, 24 Apr 2017 13:34:41 -0700 Subject: [PATCH] Edited ch07.asciidoc with Atlas code editor --- ch07.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch07.asciidoc b/ch07.asciidoc index e01d4d55..a42a660f 100644 --- a/ch07.asciidoc +++ b/ch07.asciidoc @@ -332,7 +332,7 @@ Transaction inputs with +nSequence+ values less than 2^31^ are interpreted as ha The +nSequence+ value is specified in either blocks or seconds, but in a slightly different format than we saw used in +nLocktime+. A type-flag is used to differentiate between values counting blocks and values counting time in seconds. The type-flag is set in the 23rd least significant bit (i.e., value 1<<22). If the type-flag is set, then the +nSequence+ value is interpreted as a multiple of 512 seconds. If the type-flag is not set, the +nSequence+ value is interpreted as a number of blocks. -When interpreting +nSequence+ as a relative timelock, only the 16 least significant bits are considered. Once the flags (bits 32 and 23) are evaluated, the +nSequence+ value is usually "masked" with a 16-bit mask (eg. +nSequence+ & 0x0000FFFF). +When interpreting +nSequence+ as a relative timelock, only the 16 least significant bits are considered. Once the flags (bits 32 and 23) are evaluated, the +nSequence+ value is usually "masked" with a 16-bit mask (e.g., +nSequence+ & 0x0000FFFF). <> shows the binary layout of the +nSequence+ value, as defined by BIP-68.