diff --git a/bip-tapscript.mediawiki b/bip-tapscript.mediawiki
index f4aaf34b90..a40cfc8d44 100644
--- a/bip-tapscript.mediawiki
+++ b/bip-tapscript.mediawiki
@@ -59,7 +59,6 @@ Validation of such inputs must be equivalent to performing the following steps i
* Given that OP_SUCCESSx
even causes potentially unparseable scripts to pass, it can be used to introduce multi-byte opcodes, or even a completely new scripting language when prefixed with a specific OP_SUCCESSx
opcode..
## If any push opcode fails to decode because it would extend past the end of the tapscript, fail.
# If the size of any element in the '''initial stack''' as defined in bip-taproot (i.e., the witness stack after removing both the optional annex and the two last stack elements after that) is bigger than 520 bytes, fail.
-# If the tapscript is bigger than 10000 bytes, fail.
# The tapscript is executed according to the rules in the following section, with the initial stack as input.
## If execution fails for any reason, fail.
## If the execution results in anything but exactly one element on the stack which evaluates to true with CastToBool()
, fail.
@@ -92,7 +91,7 @@ The following rules apply to OP_CHECKSIG
, OP_CHECKSIGVERIFY
*** For OP_CHECKSIGVERIFY
, the script MUST fail and terminate immediately.
*** For OP_CHECKSIG
, an empty vector is pushed onto the stack, and execution continues with the next opcode.
*** For OP_CHECKSIGADD
, a CScriptNum
with value n
is pushed onto the stack, and execution continues with the next opcode.
-** If the signature is not the empty vector, the sigops_passed
counter is incremented (see further)
+** If the signature is not the empty vector, the opcode is counted towards the sigops budget (see further).
*** For OP_CHECKSIGVERIFY
, execution continues without any further changes to the stack.
*** For OP_CHECKSIG
, a 1-byte value 0x01
is pushed onto the stack.
*** For OP_CHECKSIGADD
, a CScriptNum
with value of n + 1
is pushed onto the stack.