OP_CHECKMULTISIG is disabled in Tapscript
ProvedBitcoinTaproot.checkmultisig_rejectedFor every context, execution data, execution flag and state, tapExecOp on OP_CHECKMULTISIG and on OP_CHECKMULTISIGVERIFY is none (SCRIPT_ERR_TAPSCRIPT_CHECKMULTISIG).
import Definitions.Def_BitcoinTaproot import Definitions.Def_BitcoinScript open BitcoinTaproot BitcoinSer BitcoinSig BitcoinVerify open BitcoinScript hiding Bytes Byte
theorem BitcoinTaproot.checkmultisig_rejected (c : TapCtx) (ed : ExecData) (fExec : Bool) (ts : TapState) :
BitcoinTaproot.tapExecOp c ed fExec BitcoinScript.OP_CHECKMULTISIG ts = none ∧
BitcoinTaproot.tapExecOp c ed fExec BitcoinScript.OP_CHECKMULTISIGVERIFY ts = none := by sorryRead-back
What the Lean code literally says, in plain math · claude-fable-5-1 (independent sub-agent, blind: Lean code + auditor instructions only)
Read-back: BitcoinTaproot.checkmultisig_rejected
Binders. : a TapCtx record (interpreter flags cltv, csv, nulldummy : Booleans; a transaction ; a list of outputs; an input index ); : an ExecData record (annexPresent : Boolean, annexHash, tapleafHash : byte strings, codeseparatorPos : natural); : a Boolean; : a TapState record (an interpreter state with main stack, alt stack, condition stack vfExec and op count; an integer weightLeft; naturals codeseparatorPos and opcodePos).
Hypotheses. None.
Conclusion. Both of the following hold:
where is OP_CHECKMULTISIG and is OP_CHECKMULTISIGVERIFY as 8-bit values, and is the "script failure" result of the optional return type.
Unfolded: dispatches on the opcode byte in this order: (i) if it is OP_IF () or OP_NOTIF (), the minimal-if-guarded conditional; (ii) if it is OP_CHECKSIG () or OP_CHECKSIGVERIFY (), the Tapscript signature check; (iii) if it is OP_CHECKSIGADD (), the add-variant; (iv) if it is or , the result is unconditionally; (v) if it is OP_CODESEPARATOR (), record the opcode position; (vi) otherwise, delegate to the legacy per-opcode interpreter. The two opcodes named fall into case (iv), and the result does not depend on , on the stack contents, on the weight, or on any other field.
Edge cases the quantifiers include. (an unexecuted branch; the function itself still returns , though the surrounding step function would only call it for opcodes in the range – when not executing); empty stacks; negative weightLeft; arbitrary .
Confirmed by the mission captain (proposal self-audit).
Confirmed by the moderator at approval.