Why it exists
BIP 342 defines Tapscript: the initial script language for Taproot script-path spends. BIP 341 proves that a revealed leaf belongs to an output; Tapscript determines whether the supplied signatures and other witness data satisfy that leaf. These are distinct checks in validating a spend.
How it works
Tapscript changes signature checks to use BIP 340 Schnorr signatures and the Taproot signing message. It disables the older CHECKMULTISIG operations and introduces CHECKSIGADD, which can count valid signatures for threshold conditions. It also changes resource limits and conditional-expression rules.
A spender supplies the selected script and witness stack along with the Taproot control block. The node verifies the commitment and then evaluates the script. Upgrade mechanisms, including reserved OP_SUCCESS operations and key types, allow future soft forks to add behavior; they are not instructions for wallet authors to improvise new spending rules.
A practical example
A three-key leaf can require signatures from any two keys using CHECKSIGADD-based checks. Spending that leaf reveals the script and the signatures needed for the two-of-three condition. That differs from a MuSig2 key-path spend: MuSig2 aggregates a fixed participant set into one signature, while this Tapscript example expresses a threshold in the script itself.
What to keep in mind
Reusing a legacy multisig script unchanged is not valid Tapscript. Wallets must construct the correct script, signatures and witness ordering. Revealing a leaf exposes its conditions, and unused upgrade operations can have surprising permissive behavior under current consensus rules.
Status & implementation
Tapscript is part of the activated Taproot consensus upgrade. Bitcoin Core documents its validation alongside BIPs 340 and 341; wallet support for arbitrary script policies remains a separate question.
Specification status: Deployed · Sources checked 13 November 2026
