From 6f992463ac7726662021d17fb9850e68837c4eb2 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 00:49:41 +0000 Subject: [PATCH] Edited ch06_transactions.adoc with Atlas code editor --- ch06_transactions.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc index 1be2629c..01e28f81 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -406,7 +406,7 @@ and using scripts in detail in <>. [[sequence]] ==== Sequence -The final four bytes of an input are its _sequence_ number. +The ((("transactions", "inputs", "sequence field", id="transaction-input-sequence")))((("inputs", "sequence field", id="input-transaction-sequence")))((("sequence field (transaction inputs)", id="sequence-field")))final four bytes of an input are its _sequence_ number. The use and meaning of this field has changed over time. [[original_tx_replacement]] @@ -574,7 +574,7 @@ as defined by BIP68. image::images/mbc3_0603.png["BIP68 definition of sequence encoding"] Note that any transaction which sets a relative timelock using sequence -also sends the signal for opt-in replace by fee ((("transactions", "inputs", startref="transaction-input")))((("inputs", startref="input-transaction")))as described in +also sends the signal for opt-in replace by fee ((("transactions", "inputs", startref="transaction-input")))((("inputs", startref="input-transaction")))((("transactions", "inputs", "sequence field", startref="transaction-input-sequence")))((("inputs", "sequence field", startref="input-transaction-sequence")))((("sequence field (transaction inputs)", startref="sequence-field")))as described in <>. === Outputs