Taproot
Reading as Holder. What matters when you hold your own coins.8 of 27 claims
What it isCurious
BIP 341, the main Taproot specification, states that its aim is to improve the privacy, efficiency and flexibility of Bitcoin's scripting capabilities.1: open 1 source
FactCuriousEstablishedMedium confidence
T1BIP 341, TaprootBIP, says this directly
This proposal aims to improve privacy, efficiency, and flexibility of Bitcoin's scripting capabilities without adding new
Motivation, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 1/1History, hash and citation
Addresses and activationUser
On Bitcoin mainnet, a Taproot (P2TR) address starts with "bc1p" and is 62 characters long, and it is encoded with bech32m, the address format BIP 350 defines for SegWit version 1 and later outputs.2: open 2 sources
FactUserEstablishedMedium confidence
T2learnmeabitcoin.com, P2TRDocumentation, says this directly
A P2TR address always starts with bc1p and is 62 characters in length.
Address section, read 2026-11-20
T1BIP 350, Bech32m format for v1+ witness addressesBIP, says this directly
If its witness version is 1 or higher, encode it using Bech32m.
Specification, addresses for segregated witness outputs, read 2026-11-20
BIP 350's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0350.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1History, hash and citation
Taproot activated on Bitcoin mainnet at block 709,632, which was mined on 14 November 2021 with a block timestamp of 05:15:27 UTC.3: open 4 sources
EventUserEstablishedHigh confidence
T1BIP 341, TaprootBIP, says this directly
The deployment did activate at height 709632 on Bitcoin mainnet.
Deployment, read 2026-11-20
T2Bitcoin Optech Newsletter #175Bitcoin Optech, says this directly
as expected, the taproot soft fork activated at block height 709,632.
News, Taproot activated, read 2026-11-20
T1Bitcoin Core v22.0 src/chainparams.cpp, CMainParamsSource code, supports part of it
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].min_activation_height = 709632;
CMainParams, DEPLOYMENT_TAPROOT min_activation_height, read 2026-11-20
T1Block 709,632The chain, says this directly
Block 709,632 header, timestamp 1636866927, read 2026-11-20
Block 709,632 has hash 0000000000000000...
Run it yourself
bitcoin-cli getblockhash 709632Block 709,632's header has time = 1636866927.
Run it yourself
bitcoin-cli getblockheader $(bitcoin-cli getblockhash 709632) | grep '"time"'bitcoin/bitcoin at a0988140b7 contains this text in src/chainparams.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a0988140b71485ad12c3c3a4a9573f7c21b1eff8:src/chainparams.cpp | grep -nF 'consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].min_activation_height = 709632;'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 4/4, code 1/1, chain 2/2 (esplora pair agreed)History, hash and citation
Privacy and efficiencyHolder
When a Taproot output is spent with its key path (a signature for the output's public key), the spend does not reveal whether any alternative script conditions existed for that output.4: open 2 sources
How it worksHolderEstablishedHigh confidence
T1BIP 341, TaprootBIP, says this directly
As long as the key-based spending path is used for spending, it is not revealed whether a script path was permitted as well
Design, Taproot, read 2026-11-20
T2Bitcoin Optech topic, TaprootBitcoin Optech, says this directly
a signature that verifies against the public key (allowing the scripts to be kept private).
Topic summary, second paragraph, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
When a Taproot output is spent through one of its committed scripts, only that script is published on chain and the other committed scripts stay hidden, though the spend does show that a script path existed and that the key path was not used.5: open 3 sources
How it worksHolderEstablishedMedium confidence
T1BIP 341, TaprootBIP, says this directly
Taproot improves the privacy of Bitcoin because instead of revealing all possible conditions for spending an output,
Security, read 2026-11-20
T1BIP 341, TaprootBIP, says this directly
A script path spend leaks that there is a script path and that the key path was not applicable
Security, script path leakage, read 2026-11-20
T2Bitcoin Optech topic, TaprootBitcoin Optech, supports part of it
to allow committing to more than one script, any one of which may be used at spend time.
Topic summary, second paragraph, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3History, hash and citation
A Taproot output controlled by several signers through key aggregation, such as MuSig2 (BIP 327), can be spent with one aggregate key and one signature, so on chain it is indistinguishable from a single-signer Taproot output.6: open 2 sources
How it worksHolderEstablishedHigh confidence
T1BIP 327, MuSig2 for BIP340-compatible Multi-SignaturesBIP, says this directly
MuSig2 Taproot outputs are indistinguishable for a blockchain observer from regular, single-signer Taproot outputs
Motivation, read 2026-11-20
T1BIP 341, TaprootBIP, says this directly
Such multi-party public keys and signatures are indistinguishable from their single-party equivalents.
Design, Schnorr signature validation, read 2026-11-20
BIP 327's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0327.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1History, hash and citation
A Taproot key path spend reveals no script: its witness carries a single Schnorr signature, checked against the 32-byte public key already in the output being spent.7: open 3 sources
How it worksHolderEstablishedHigh confidence
T1BIP 341, TaprootBIP, says this directly
If there is exactly one element left in the witness stack, key path spending is used:
Specification, Script validation rules, read 2026-11-20
T1BIP 340, Schnorr Signatures for secp256k1BIP, supports part of it
Encoding only the X coordinate, resulting in 32-byte public keys and 64-byte signatures.
Design, encoding choices, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, VerifyWitnessProgramSource code, says this directly
if (!checker.CheckSchnorrSignature(stack.front(), program, SigVersion::TAPROOT, execdata, serror)) {
VerifyWitnessProgram, Taproot key path branch, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'if (!checker.CheckSchnorrSignature(stack.front(), program, SigVersion::TAPROOT, execdata, serror)) {'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1History, hash and citation
The specificationsBuilder
The Taproot soft fork consists of three BIPs deployed together: BIP 340 for Schnorr signatures, BIP 341 for the spending rules of SegWit version 1 outputs, and BIP 342 for Tapscript, the script language used inside Taproot.8: open 3 sources
FactBuilderEstablishedHigh confidence
T2Bitcoin Optech Newsletter #153Bitcoin Optech, says this directly
the taproot soft fork and related changes specified in BIPs 340, 341, and 342 were locked in by signaling miners
News, Taproot locked in, read 2026-11-20
T1Bitcoin Core v22.0 src/chainparams.cpp, CMainParamsSource code, says this directly
// Deployment of Taproot (BIPs 340-342)
CMainParams, Taproot deployment comment, read 2026-11-20
T1BIP 342, Validation of Taproot ScriptsBIP, supports part of it
This document specifies the semantics of the initial scripting system under [[bip-0341.mediawiki|BIP341]].
Abstract, read 2026-11-20
bitcoin/bitcoin at a0988140b7 contains this text in src/chainparams.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a0988140b71485ad12c3c3a4a9573f7c21b1eff8:src/chainparams.cpp | grep -nF '// Deployment of Taproot (BIPs 340-342)'BIP 342's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0342.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 2/2History, hash and citation
BIP 340 specifies the Schnorr signatures Taproot uses: 64-byte signatures over the secp256k1 curve, verified against 32-byte public keys that encode only the X coordinate of the curve point.9: open 2 sources
DefinitionBuilderEstablishedMedium confidence
T1BIP 340, Schnorr Signatures for secp256k1BIP, says this directly
This document proposes a standard for 64-byte Schnorr signatures over the elliptic curve
Abstract, read 2026-11-20
T1BIP 340, Schnorr Signatures for secp256k1BIP, says this directly
Encoding only the X coordinate, resulting in 32-byte public keys and 64-byte signatures.
Design, encoding choices, read 2026-11-20
BIP 340's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0340.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1History, hash and citation
BIP 340 describes Schnorr signatures as linear, a property that lets several collaborating parties produce one signature that is valid for the sum of their public keys.10: open 2 sources
How it worksBuilderEstablishedMedium confidence
T1BIP 340, Schnorr Signatures for secp256k1BIP, says this directly
to produce a signature that is valid for the sum of their public keys.
Motivation, Linearity, read 2026-11-20
T2Bitcoin Optech topic, TaprootBitcoin Optech, supports part of it
Taproot uses schnorr signatures that simplify multiparty construction (e.g. using MuSig) and MAST
Topic summary, second paragraph, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
Taproot (BIP 341) defines rules for SegWit witness version 1: a Taproot output is a native SegWit output with witness version 1 and a 32-byte program, which Bitcoin Core checks in VerifyWitnessProgram.11: open 2 sources
TraceBuilderEstablishedHigh confidence
T1BIP 341, TaprootBIP, says this directly
A Taproot output is a native SegWit output
Specification, Script validation rules, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, VerifyWitnessProgramSource code, says this directly
} else if (witversion == 1 && program.size() == WITNESS_V1_TAPROOT_SIZE && !is_p2sh) {
VerifyWitnessProgram, witness version 1 branch, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF '} else if (witversion == 1 && program.size() == WITNESS_V1_TAPROOT_SIZE && !is_p2sh) {'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.h.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.h | grep -nF 'inline constexpr size_t WITNESS_V1_TAPROOT_SIZE = 32;'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 2/2History, hash and citation
BIP 341 chooses between the two ways of spending a Taproot output by counting witness elements after removing any annex: exactly one element means a key path spend, and two or more mean a script path spend.12: open 3 sources
How it worksBuilderEstablishedHigh confidence
T1BIP 341, TaprootBIP, says this directly
If there is exactly one element left in the witness stack, key path spending is used:
Specification, Script validation rules, key path, read 2026-11-20
T1BIP 341, TaprootBIP, says this directly
If there are at least two witness elements left, script path spending is used:
Specification, Script validation rules, script path, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, VerifyWitnessProgramSource code, says this directly
if (stack.size() >= 2 && !stack.back().empty() && stack.back()[0] == ANNEX_TAG) {
VerifyWitnessProgram, Taproot branch, annex detection, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'if (stack.size() >= 2 && !stack.back().empty() && stack.back()[0] == ANNEX_TAG) {'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1History, hash and citation
For a Taproot output with a script tree, the output key is an internal public key tweaked with the tree's Merkle root, and Bitcoin Core checks a script path spend in VerifyTaprootCommitment by recomputing that root and verifying the tweak.13: open 2 sources
TraceBuilderEstablishedHigh confidence
T1Bitcoin Core src/script/interpreter.cpp, VerifyTaprootCommitmentSource code, says this directly
// Verify that the output pubkey matches the tweaked internal pubkey, after correcting for parity.
VerifyTaprootCommitment, read 2026-11-20
T1BIP 341, TaprootBIP, supports part of it
of a Merkle tree whose leaves consist of a version number and a script.
Informal design overview, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'const uint256 merkle_root = ComputeTaprootMerkleRoot(control, tapleaf_hash);'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'return q.CheckTapTweak(p, merkle_root, control[0] & 1);'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 2/2History, hash and citation
Each leaf of a Taproot script tree pairs a script with a leaf version, so later soft forks can introduce new script versions; Tapscript as defined in BIP 342 uses leaf version 0xc0.14: open 2 sources
How it worksBuilderEstablishedHigh confidence
T1BIP 341, TaprootBIP, says this directly
new script versions can be introduced with a soft fork while remaining compatible with BIP 341.
Design, future extensions, read 2026-11-20
T1Bitcoin Core src/script/interpreter.h, Taproot constantsSource code, says this directly
inline constexpr uint8_t TAPROOT_LEAF_TAPSCRIPT = 0xc0;
TAPROOT_LEAF_TAPSCRIPT, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.h | grep -nF 'inline constexpr uint8_t TAPROOT_LEAF_TAPSCRIPT = 0xc0;'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'if ((control[0] & TAPROOT_LEAF_MASK) == TAPROOT_LEAF_TAPSCRIPT) {'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 2/2History, hash and citation
BIP 342 Tapscript disables OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY and adds OP_CHECKSIGADD (opcode 0xba), which checks one signature and adds the result to a running count, so threshold scripts check signatures one at a time.15: open 3 sources
How it worksBuilderEstablishedHigh confidence
T1BIP 342, Validation of Taproot ScriptsBIP, says this directly
The following script opcodes are disabled in tapscript:
Specification, rules for signature opcodes, read 2026-11-20
T1BIP 342, Validation of Taproot ScriptsBIP, says this directly
The opcode 186 (<code>0xba</code>) is named as <code>OP_CHECKSIGADD</code>.
Specification, OP_CHECKSIGADD, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, EvalScript, OP_CHECKSIGADDSource code, says this directly
stack.push_back((num + (success ? 1 : 0)).getvch());
EvalScript, case OP_CHECKSIGADD, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'if (sigversion == SigVersion::TAPSCRIPT) return set_error(serror, SCRIPT_ERR_TAPSCRIPT_CHECKMULTISIG);'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'case OP_CHECKSIGADD:'BIP 342's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0342.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 3/3History, hash and citation
In the codeBuilder
The BIP 341 signature message for Taproot spends is computed in Bitcoin Core by SignatureHashSchnorr in src/script/interpreter.cpp, which hashes it with the BIP 340 tagged hash "TapSighash".16: open 2 sources
TraceBuilderEstablishedHigh confidence
T1Bitcoin Core src/script/interpreter.cpp, SignatureHashSchnorrSource code, says this directly
bool SignatureHashSchnorr(uint256& hash_out, ScriptExecutionData& execdata, const T& tx_to, uint32_t in_pos,
SignatureHashSchnorr, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, tagged hash writersSource code, says this directly
const HashWriter HASHER_TAPSIGHASH{TaggedHash("TapSighash")};
HASHER_TAPSIGHASH, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'bool SignatureHashSchnorr(uint256& hash_out, ScriptExecutionData& execdata, const T& tx_to, uint32_t in_pos,'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'const HashWriter HASHER_TAPSIGHASH{TaggedHash("TapSighash")};'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 2/2History, hash and citation
Bitcoin Core PR #19953, which implemented validation of BIP 340, BIP 341 and BIP 342, was merged on 15 October 2020 without any signing or wallet support.17: open 1 source
EventBuilderEstablishedMedium confidence
T1Bitcoin Core PR #19953, Implement BIP 340-342 validation (Schnorr/taproot/tapscript)Pull request, says this directly
No signing or wallet support of any kind is included, as testing is done entirely through the Python test framework.
Pull request description; merged 2020-10-15T08:23:21Z, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 1/1History, hash and citation
Tapscript and tree detailsResearcher
In a Taproot script path spend, the last witness element is the control block: 33 bytes plus 32 bytes for each Merkle path node, and Bitcoin Core accepts at most 128 path nodes, which limits a script tree to a depth of 128.18: open 2 sources
How it worksResearcherEstablishedHigh confidence
T1BIP 341, TaprootBIP, says this directly
The last stack element is called the control block
Specification, Script validation rules, script path, read 2026-11-20
T1Bitcoin Core src/script/interpreter.h, Taproot constantsSource code, says this directly
inline constexpr size_t TAPROOT_CONTROL_MAX_NODE_COUNT = 128;
TAPROOT_CONTROL_MAX_NODE_COUNT, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.h | grep -nF 'inline constexpr size_t TAPROOT_CONTROL_BASE_SIZE = 33;'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.h | grep -nF 'inline constexpr size_t TAPROOT_CONTROL_NODE_SIZE = 32;'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.h | grep -nF 'inline constexpr size_t TAPROOT_CONTROL_MAX_NODE_COUNT = 128;'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 3/3History, hash and citation
BIP 342 renames opcode numbers 80, 98, 126 to 129, 131 to 134, 137, 138, 141, 142, 149 to 153 and 187 to 254 as OP_SUCCESSx: if a Tapscript contains any of them, validation succeeds without applying the other rules, which BIP 342 describes as a mechanism to upgrade the Script system.19: open 3 sources
How it worksResearcherEstablishedMedium confidence
T1BIP 342, Validation of Taproot ScriptsBIP, says this directly
is encountered, validation succeeds (none of the rules below apply).
Specification, OP_SUCCESSx, read 2026-11-20
T1BIP 342, Validation of Taproot ScriptsBIP, says this directly
80, 98, 126-129, 131-134, 137-138, 141-142, 149-153, 187-254
Specification, OP_SUCCESSx opcode list, read 2026-11-20
T1BIP 342, Validation of Taproot ScriptsBIP, says this directly
is a mechanism to upgrade the Script system.
Specification, OP_SUCCESSx footnote, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3History, hash and citation
BIP 342 removes two limits of earlier Bitcoin script for Tapscript: the maximum script size of 10,000 bytes and the limit of 201 non-push opcodes per script.20: open 2 sources
FactResearcherEstablishedMedium confidence
T1BIP 342, Validation of Taproot ScriptsBIP, says this directly
The maximum script size of 10000 bytes does not apply.
Specification, Resource limits, script size limit, read 2026-11-20
T1BIP 342, Validation of Taproot ScriptsBIP, says this directly
The maximum non-push opcodes limit of 201 per script does not apply.
Specification, Resource limits, non-push opcodes limit, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
Activation historyResearcher
Taproot was activated with Speedy Trial, a variant of BIP 9 version bits signaling: if 90% of blocks (1,815 of 2,016) in a retarget period signaled on bit 2 between 24 April and 11 August 2021, Taproot would lock in and then activate no earlier than block 709,632.21: open 4 sources
How it worksResearcherEstablishedHigh confidence
T1Bitcoin Core 0.21.1 release notesRelease notes, says this directly
Activation for taproot is being managed using a variation of BIP9 versionbits called Speedy Trial (described in BIP341).
Taproot soft fork, read 2026-11-20
T1Bitcoin Core 0.21.1 release notesRelease notes, says this directly
If 90% of blocks within a 2,016-block retarget period (about two weeks) signal support for taproot
Taproot soft fork, threshold, read 2026-11-20
T1BIP 341, TaprootBIP, says this directly
For Bitcoin mainnet, the starttime is epoch timestamp 1619222400 (midnight 24 April 2021 UTC), timeout is
Deployment, read 2026-11-20
T1Bitcoin Core v22.0 src/chainparams.cpp, CMainParamsSource code, says this directly
consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].bit = 2;
CMainParams, DEPLOYMENT_TAPROOT, read 2026-11-20
bitcoin/bitcoin at a0988140b7 contains this text in src/chainparams.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a0988140b71485ad12c3c3a4a9573f7c21b1eff8:src/chainparams.cpp | grep -nF 'consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].bit = 2;'bitcoin/bitcoin at a0988140b7 contains this text in src/chainparams.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a0988140b71485ad12c3c3a4a9573f7c21b1eff8:src/chainparams.cpp | grep -nF 'consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].nStartTime = 1619222400;'bitcoin/bitcoin at a0988140b7 contains this text in src/chainparams.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a0988140b71485ad12c3c3a4a9573f7c21b1eff8:src/chainparams.cpp | grep -nF 'consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].nTimeout = 1628640000;'bitcoin/bitcoin at a0988140b7 contains this text in src/chainparams.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a0988140b71485ad12c3c3a4a9573f7c21b1eff8:src/chainparams.cpp | grep -nF 'consensus.nRuleChangeActivationThreshold = 1815;'bitcoin/bitcoin at a0988140b7 contains this text in src/chainparams.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a0988140b71485ad12c3c3a4a9573f7c21b1eff8:src/chainparams.cpp | grep -nF 'consensus.vDeployments[Consensus::DEPLOYMENT_TAPROOT].min_activation_height = 709632;'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 4/4, code 5/5History, hash and citation
Taproot's Speedy Trial activation parameters were added to Bitcoin Core in PR #21686, merged on 15 April 2021, shortly after PR #21377 added Speedy Trial support to the version bits code the same day.22: open 2 sources
TraceResearcherEstablishedHigh confidence
T1Bitcoin Core PR #21686, Speedy trial activation parameters for TaprootPull request, says this directly
Adds the activation parameters for taproot as specified in https://github.com/bitcoin/bips/pull/1104
Pull request description; merged 2021-04-15T08:20:34Z, read 2026-11-20
T1Bitcoin Core PR #21377, Speedy trial support for versionbitsPull request, says this directly
BIP9-based implementation of "speedy trial" activation specification
Pull request description; merged 2021-04-15T02:05:16Z, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
Taproot locked in during June 2021: Optech Newsletter #153, published on 16 June 2021, reported that signaling miners had locked in the soft fork the previous weekend, about five months before it activated at block 709,632.23: open 2 sources
EventResearcherEstablishedMedium confidence
T2Bitcoin Optech Newsletter #153Bitcoin Optech, says this directly
the taproot soft fork and related changes specified in BIPs 340, 341, and 342 were locked in by signaling miners
News, Taproot locked in, published 2021-06-16, read 2026-11-20
T2Bitcoin Optech Newsletter #153Bitcoin Optech, supports part of it
Taproot will be safe to use after block 709,632, which is expected in early or mid November.
News, Taproot locked in, safety note, published 2021-06-16, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
Since Bitcoin Core PR #23536, merged on 25 March 2022, Bitcoin Core enforces Taproot's script rules on every block where SegWit rules apply, including blocks before 709,632, regardless of the version bits deployment status, with one exception block.24: open 3 sources
EventResearcherEstablishedHigh confidence
T1Bitcoin Core PR #23536, Enforce Taproot script flags whenever WITNESS is setPull request, says this directly
it makes sense to enforce its rules on all blocks, even historic ones, regardless of the deployment status.
Pull request description; merged 2022-03-25T13:12:03Z, read 2026-11-20
T1Bitcoin Core PR #23536, Enforce Taproot script flags whenever WITNESS is setPull request, says this directly
I found one block which fails verification with the flags applied, so I added a `TaprootException`
Pull request description, the exception, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, CMainParamsSource code, says this directly
consensus.script_flag_exceptions.emplace( // Taproot exception
CMainParams, script_flag_exceptions, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'consensus.script_flag_exceptions.emplace( // Taproot exception'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1History, hash and citation
Bitcoin Core's mainnet parameters exempt block 692,261, mined in July 2021 before Taproot activated, from Taproot script verification, checking it only with the P2SH and SegWit script flags, because that block fails the Taproot rules.25: open 3 sources
FactResearcherEstablishedHigh confidence
T1Bitcoin Core src/kernel/chainparams.cpp, CMainParamsSource code, says this directly
uint256{"0000000000000000000f14c35b2d841e986ab5441de8c585d5ffe55ea1e395ad"}, SCRIPT_VERIFY_P2SH | SCRIPT_VERIFY_WITNESS);
CMainParams, script_flag_exceptions, Taproot exception, read 2026-11-20
T1Bitcoin Core PR #23536, Enforce Taproot script flags whenever WITNESS is setPull request, says this directly
I found one block which fails verification with the flags applied, so I added a `TaprootException`
Pull request description, the exception, read 2026-11-20
T1Block 692,261The chain, says this directly
Block 692,261 header, timestamp 1627028660 (23 July 2021), read 2026-11-20
Block 692,261 has hash 0000000000000000...
Run it yourself
bitcoin-cli getblockhash 692261Block 692,261's header has time = 1627028660.
Run it yourself
bitcoin-cli getblockheader $(bitcoin-cli getblockhash 692261) | grep '"time"'bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'uint256{"0000000000000000000f14c35b2d841e986ab5441de8c585d5ffe55ea1e395ad"}, SCRIPT_VERIFY_P2SH | SCRIPT_VERIFY_WITNESS);'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1, chain 2/2 (esplora pair agreed)History, hash and citation
As of Bitcoin Core commit f498a5a6 (November 2026), the mainnet MinBIP9WarningHeight is block 711,648, which the code describes as the Taproot activation height plus one miner confirmation window (709,632 plus 2,016 blocks).26: open 1 source
TraceResearcherEstablishedHigh confidence
T1Bitcoin Core src/kernel/chainparams.cpp, CMainParamsSource code, says this directly
consensus.MinBIP9WarningHeight = 711648; // taproot activation height + miner confirmation window
CMainParams, MinBIP9WarningHeight, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'consensus.MinBIP9WarningHeight = 711648; // taproot activation height + miner confirmation window'Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 1/1, code 1/1History, hash and citation