Taproot is a coordinated upgrade to Bitcoin defined by three Bitcoin Improvement Proposals: BIP 340 specifies Schnorr signatures, BIP 341 specifies Taproot outputs and their spending paths, and BIP 342 specifies Tapscript validation. Together they allow a payment to commit to alternative spending conditions while revealing only the information needed for the chosen path.
This reference explains the deployed specifications and their limits. The proposal headers give an assignment date of January 19, 2020; the Taproot deployment activated on Bitcoin mainnet at block 709,632 in November 2021. The current BIP headers mark all three specifications as Deployed. [1–4]
Authors, Status, and Licenses
- BIP 340 — Schnorr Signatures for secp256k1: Pieter Wuille, Jonas Nick, and Tim Ruffing. The specification is licensed under BSD-2-Clause. Its reference code and test vectors separately offer BSD-2-Clause, MIT, or CC0-1.0.
- BIP 341 — Taproot: SegWit version 1 spending rules: Pieter Wuille, Jonas Nick, and Anthony Towns. Specification license: BSD-3-Clause.
- BIP 342 — Validation of Taproot Scripts: Pieter Wuille, Jonas Nick, and Anthony Towns. Specification license: BSD-3-Clause.
These are consensus specifications in the whitepaper/reference collection. Their individual licenses and roles matter when reading or reusing the original documents. [1–3]
BIP 340: Schnorr Signature Encoding and Verification
BIP 340 defines a specific Schnorr scheme over the secp256k1 curve. Its public keys are 32-byte x-only keys, interpreted using the curve point with an even Y coordinate. A signature is exactly 64 bytes: the nonce point’s X coordinate, r, followed by a scalar, s. This fixed encoding gives implementations a common, precisely defined verification rule. [1]
The challenge includes r, the public key, and the message. Conceptually, verification reconstructs R = sG − eP, where G is the curve generator, P is the public key, and e is the challenge. It also checks valid encodings and ranges, rejects the point at infinity, and requires the reconstructed point to have even Y and X coordinate r. The public key in the challenge helps protect against related-key attacks when keys are tweaked. [1]
Tagged hashes separate purposes such as nonce generation and challenge calculation. Implementations must also handle nonces carefully: reusing a nonce across signing contexts can expose the secret key. BIP 340 recommends auxiliary randomness in its single-signer construction; a multiparty signing protocol needs its own nonce rules. The current specification permits messages of arbitrary length, following its April 2023 update. Taproot transaction signatures use a separately defined 32-byte transaction digest. [1, 2]
Batch Verification and Multiparty Signing
BIP 340 also describes batch verification, combining signature equations with randomized coefficients so invalid signatures cannot simply cancel one another. This can reduce verification work, but the specification does not promise a fixed speedup or establish that every Bitcoin implementation uses batching. Batch verification still checks multiple existing signatures; it does not turn them into one on-chain signature. [1]
Schnorr’s algebra supports interactive multiparty protocols. The BIP points to MuSig2 for all-participant, or n-of-n, signing, and to separate threshold constructions for k-of-n policies. Safe key aggregation and nonce coordination require those protocols. Simply adding independently generated signatures does not provide the same guarantee. Our MuSig2 reference covers that distinct construction. [1]
BIP 341: Taproot Outputs and Spending Paths
Taproot uses a native SegWit version 1 output with a 32-byte witness program, commonly called Pay-to-Taproot (P2TR). Its output key commits to an internal public key and, when present, a Merkle root of alternative scripts. A simplified expression is Q = P + tG, where the tagged TapTweak hash derives t from the internal key and optional script-tree root; the output contains x(Q). [2]
- Key-path spend: authorization comes from a valid signature for the tweaked output key. A cooperative multiparty contract can use this path when its signing protocol produces the required signature. The transaction need not reveal its alternative scripts.
- Script-path spend: the witness supplies the chosen script, its inputs, and a control block. The control block contains the leaf-version/parity byte, internal key, and sibling hashes needed to reconstruct the commitment.
The control block is 33 + 32m bytes, with a Merkle path of at most 128 hashes. Validation checks the leaf and sorted branch hashes, the tweak, and the output key’s X coordinate and Y parity before applying the appropriate script rules. It reveals the selected script and proof, rather than every script in the tree. [2]
Transaction Signatures and the Annex
A 64-byte Taproot signature implies SIGHASH_DEFAULT, whose transaction coverage is equivalent to SIGHASH_ALL. A 65-byte signature carries an explicit permitted nonzero sighash byte; appending a zero byte is invalid. Transaction commitments depend on the selected sighash mode. Unless ANYONECANPAY applies, the common message includes all spent outputs’ amounts and scriptPubKeys, helping a signer determine the transaction’s fee from the authenticated input data. [2]
An optional final witness element beginning with 0x50 is an annex when the witness has at least two elements. It is removed before deciding between key and script paths, contributes to transaction weight, and is committed to by the signature. Its currently reserved contents are otherwise ignored by Taproot validation. This extension mechanism does not itself define a new application feature. [2]
BIP 342: Tapscript and Resource Limits
BIP 342 defines the script rules for Taproot leaves with version 0xc0. Signature-checking opcodes use BIP 340 Schnorr verification. OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY are disabled; OP_CHECKSIGADD supports counting successful individual signature checks for script-based threshold policies. That counting operation is separate from cryptographic signature aggregation. Conditional inputs to OP_IF and OP_NOTIF must satisfy the consensus MINIMALIF encoding rule. [3]
Tapscript removes the earlier 10,000-byte script-size and 201 non-push-opcode limits, while retaining important bounds. For ordinary execution, stack and altstack together are limited to 1,000 elements, individual stack elements remain limited to 520 bytes, and transaction/block weight still constrains size. A per-input signature-operation budget starts at 50 + serialized witness size and loses 50 for each executed signature opcode with a nonempty signature; a negative budget fails validation. [3]
OP_SUCCESSx reserves opcode values for future soft forks. Encountering one while decoding a valid Taproot script causes script validation to succeed before the ordinary execution and stack-limit checks, including when the opcode is in a branch that would not execute. Bytes inside pushed data are not decoded as opcodes. Earlier BIP 141/341 validity checks still apply. This behavior is an upgrade mechanism; it does not activate the prospective meanings of those opcodes. [3]
Privacy, Compatibility, and Practical Limits
Different single-key and cooperative multiparty uses can share the same P2TR key-path form. However, P2TR outputs remain distinguishable from older output types such as P2WPKH. A script-path spend reveals its script and proof depth, which can help identify wallet or contract patterns. Reuse, transaction structure, and information published elsewhere can also weaken privacy. Hidden branches are not guaranteed to remain secret forever. Taproot does not conceal transaction amounts or provide post-quantum signatures. [1, 2]
The activation used a 90% signaling threshold in a 2,016-block period, followed by the minimum activation height. Older nodes can continue operating under the soft-fork compatibility model, but they do not enforce the new Taproot spending rules. Upgraded validation is required to check those rules fully. Cross-input signature aggregation and proposed new scripting features are outside these deployed BIPs. [2–4]
Social Media Sentiment
No current social-media discussion sample was collected for this technical reference, so no community sentiment score or consensus is asserted. The review above uses the specifications and Bitcoin Core’s activation documentation. Claims about wallet adoption, usage percentages, or public enthusiasm would need their own dated evidence.
Last updated: 2026-10
Related Terms
- Bitcoin — the network whose spending rules these proposals extend.
- SegWit — the witness framework within which native Taproot outputs operate.
See Also
- Bitcoin Script and Taproot — a broader introduction to Bitcoin’s spending language.
- MuSig2 — the separate multiparty Schnorr signing construction.
- Bitcoin Whitepaper — the original peer-to-peer electronic cash proposal.
Sources
- Pieter Wuille, Jonas Nick, and Tim Ruffing. BIP 340: Schnorr Signatures for secp256k1. Official specification for encoding, signing, verification, batching, application boundaries, licenses, and later changes.
- Pieter Wuille, Jonas Nick, and Anthony Towns. BIP 341: Taproot — SegWit version 1 spending rules. Official specification for output commitments, witnesses, sighash coverage, privacy limits, deployment, and compatibility.
- Pieter Wuille, Jonas Nick, and Anthony Towns. BIP 342: Validation of Taproot Scripts. Official Tapscript rules covering signature opcodes, extension mechanisms, and resource limits.
- Bitcoin Core. Bitcoin Core 0.21.1 release announcement, May 1, 2021. Explains the signaling threshold, delayed activation height, and availability of Taproot activation logic.