2026-11-20-seed-taproot
Published
26 claims
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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".
- 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.
- 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.
- 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.
- 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.
- 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).
- Taproot is a soft fork upgrade to Bitcoin, active since November 2021, that adds a new kind of output whose coins can be spent either with a single signature or by revealing one of several spending conditions committed to in advance.
- BIP 341, the main Taproot specification, states that its aim is to improve the privacy, efficiency and flexibility of Bitcoin's scripting capabilities.
Held for the owner
Their text stays private until the owner approves it.
- 2 claims on taproot
names Murch
Rejected
6 candidates
- Taproot locked in at a specific block height in June 2021.
research: No fetched primary gave the lock-in height; only Optech's "last weekend" wording was available.
- BIP 342 sets a signature-operation budget of 50 plus the input's witness size.
research: Raw wiki markup around the sentence was not confirmed, so an exact quote could not be guaranteed.
- The Taproot output key is Q = P + int(t)G with t = hashTapTweak(p || km).
research: The BIP 341 lines are heavy with wiki markup; the claim was written against VerifyTaprootCommitment instead.
- Schnorr signatures are provably secure under weaker assumptions than ECDSA.
research: Raw markup of the BIP 340 sentence was not confirmed; lower priority.
- P2TR share of output value or daily transactions from analytics dashboards (Coinglass, Spark).
research: T3/T4-style dashboards without stable dated snapshots; preferred the dated mailing-list figures.
- Which Bitcoin Core PR removed DEPLOYMENT_TAPROOT from chainparams entirely.
research: Not researched in this run; the burial claim rests on PR
Could not settle
- The CLAIMS.md example cites "min_activation_height = 709632" in src/kernel/chainparams.cpp at master; that text is absent at f498a5a6. The example should cite the v22.0 commit a0988140 and src/chainparams.cpp.
- Exact lock-in block of Taproot (end of the signaling period in June 2021); settle with getblockchaininfo history or version bits data from the chain.
- The PR that removed the Taproot deployment entry from chainparams after PR
- Fresher adoption figures than July 2025, with a method; a reproducible query against the chain would settle it.
- In Murch's message, "KP" and "SP" were read as key path and script path; the message's footnote 4 should be checked to confirm.
Injection attempts
No text in any source this run read tried to give the brain orders.
Read
25 sources
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0341.mediawiki
Taproot spending rules, key and script paths, control block, privacy, deployment section
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0340.mediawiki
Schnorr signature sizes, x-only keys, linearity
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0342.mediawiki
Tapscript opcode changes, OP_SUCCESSx, removed limits
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0350.mediawiki
bech32m for witness version 1 and later
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0327.mediawiki
MuSig2 outputs indistinguishable from single-signer outputs
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/kernel/chainparams.cpp
Taproot exception block, MinBIP9WarningHeight; confirmed no DEPLOYMENT_TAPROOT or 709632 on master
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/script/interpreter.cpp
SignatureHashSchnorr, VerifyTaprootCommitment, key path check, annex, OP_CHECKSIGADD
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/script/interpreter.h
Taproot leaf and control block constants
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/release-notes/release-notes-0.21.1.md
Speedy Trial description and parameters
- https://raw.githubusercontent.com/bitcoin/bitcoin/a0988140b71485ad12c3c3a4a9573f7c21b1eff8/src/chainparams.cpp
Taproot deployment parameters as shipped in v22.0
- https://api.github.com/repos/bitcoin/bitcoin/git/tags/87c63779d2119cf854d37520f169694f1a3da558
confirmed tag v22.0 points to commit a0988140b71485ad12c3c3a4a9573f7c21b1eff8
- https://api.github.com/repos/bitcoin/bitcoin/pulls/19953
implementation PR, merge date
- https://api.github.com/repos/bitcoin/bitcoin/pulls/21377
Speedy Trial version bits support
- https://api.github.com/repos/bitcoin/bitcoin/pulls/21686
Taproot Speedy Trial parameters
- https://api.github.com/repos/bitcoin/bitcoin/pulls/23536
burial of the Taproot deployment and the exception block
- https://blockstream.info/api/block-height/709632
hash of block 709,632 (agreed with mempool.space)
- https://mempool.space/api/block-height/709632
hash of block 709,632
- https://blockstream.info/api/block/0000000000000000000687bca986194dc2c1f949318629b44bb54ec0a94d8244
timestamp of block 709,632
- https://blockstream.info/api/block/0000000000000000000f14c35b2d841e986ab5441de8c585d5ffe55ea1e395ad
height and timestamp of the Taproot exception block
- https://bitcoinops.org/en/topics/taproot/
expert summary of Taproot
- https://bitcoinops.org/en/newsletters/2021/11/17/
Newsletter
- https://bitcoinops.org/en/newsletters/2021/06/16/
Newsletter
- https://learnmeabitcoin.com/technical/script/p2tr/
bc1p prefix and 62-character length
- https://mailing-list.bitcoindevs.xyz/bitcoindev/a40c2b1a-1164-4794-a6d5-79d0b97296aa@murch.one/
dated P2TR adoption figures (July 2025)
- https://mailing-list.bitcoindevs.xyz/bitcoindev/2c16b2d0-ac82-4c10-8404-02001bda2658n@googlegroups.com/
reply quoting the same figures; used only to find the original message