From cf05a86d06410a8208cad2e8d27164678bc748d7 Mon Sep 17 00:00:00 2001 From: Rishabh Date: Tue, 2 Jul 2024 22:56:48 +0530 Subject: [PATCH] fix(ch6): mention `OP_CHECKSEQUENCEVERIFY` repurposed `OP_NOP3` --- ch06_transactions.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc index cef3a68d..22f50e2a 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -100,7 +100,7 @@ change to Bitcoin's consensus rules. BIP68 places additional constraints on the sequence field, but those constraints only apply to transactions with version 2 or higher. Version 1 transactions are unaffected. BIP112, which was part of the same soft fork as BIP68, -introduced an opcode (++OP_CHECKSEQUENCEVERIFY++), which will now fail if it is +repurposed OP_NOP3 to introduce a new opcode (++OP_CHECKSEQUENCEVERIFY++), which will now fail if it is evaluated as part of a transaction with a version less than 2. Beyond those two changes, version 2 transactions are identical to version 1 transactions.