From 0c44ee53cd6be001065422cd77109241c16f525c Mon Sep 17 00:00:00 2001 From: clenser Date: Sat, 28 Oct 2023 18:43:22 +0000 Subject: [PATCH] Edited ch07_authorization-authentication.adoc with Atlas code editor --- ch07_authorization-authentication.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch07_authorization-authentication.adoc b/ch07_authorization-authentication.adoc index 976d8a82..ccb576af 100644 --- a/ch07_authorization-authentication.adoc +++ b/ch07_authorization-authentication.adoc @@ -383,7 +383,7 @@ script may include multiple of those opcodes. [[multisig_bug]] ==== An Oddity in CHECKMULTISIG Execution -There ((("OP_CHECKMULTISIG execution", id="op-checkmultisig")))((("CHECKMULTISIG execution", id="checkmultisig")))is an oddity in +There ((("OP_CHECKMULTISIG execution", id="op-checkmultisig")))is an oddity in ++OP_CHECKMULTISIG++'s execution that requires a slight workaround. When +OP_CHECKMULTISIG+ executes, it should consume _t_ + _k_ + 2 items on the stack as parameters. However, due to the oddity, +OP_CHECKMULTISIG+ will pop an extra @@ -463,7 +463,7 @@ book, we simply call it an oddity. From now on, if you see a multisig script, you should expect to see an extra +OP_0+ in the beginning, whose only purpose is as a -workaround to an oddity in the ((("scripts", "multisignature", startref="script-multisignature")))((("multisignature scripts", startref="multi-script")))((("OP_CHECKMULTISIG execution", startref="op-checkmultisig")))((("CHECKMULTISIG execution", startref="checkmultisig")))consensus rules. +workaround to an oddity in the ((("scripts", "multisignature", startref="script-multisignature")))((("multisignature scripts", startref="multi-script")))((("OP_CHECKMULTISIG execution", startref="op-checkmultisig")))consensus rules. [[p2sh]] === Pay to Script Hash