TERM_DEF // UPGRADES_BIPS / TAPROOT_BIP_341
TAPROOT (BIP
341)
341)
Taproot (BIP 341). The 2021 upgrade introducing key-aggregable schnorr-signatures/">Schnorr signatures and Merkleized script trees.
This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.
This page sits in the Upgrades & BIPs section — The proposal process and the major upgrades that shaped Bitcoin. Read on for what it is, why it exists, how it works under the hood, and what to watch out for.
WHAT_TAPROOT_BIP_341_IS
Taproot (BIP 341) — at a glance
UPGRADES
BIP 341 is a proposal in the Script family, first published in 2020 with status final (fork/">soft fork). The 2021 upgrade introducing key-aggregable Schnorr signatures and Merkleized script trees. Its technical mechanism: Taproot — P2TR output is a single 32-byte tweaked pubkey hiding a MAST tree. every "bc1p..." address; on-chain footprint identical to a single key
Why it exists
DESIGN
Taproot (BIP 341) exists to solve a specific problem: unify single-sig + multi-sig + script-path spending in one tweaked-key output. Without a written, numbered spec, every wallet and node implementer would interpret the requirement differently — and Bitcoin's value depends on every implementation agreeing exactly. BIP-341 is the single source of truth for this concern, so any new client built today can match the behaviour of every client built since 2020.
HOW_IT_WORKS
Mechanism
HOW IT WORKS
Mechanically, BIP-341 taproot — P2TR output is a single 32-byte tweaked pubkey hiding a MAST tree. Because this is a soft fork, old software accepts new behaviour without modification — but new behaviour is rejected if old software produces it. Adoption today: every "bc1p..." address; on-chain footprint identical to a single key.
1. Author drafts BIP-341 against the BIP-2 template — abstract, motivation, specification, rationale.
2. The text + a reference implementation are posted on the bitcoin-dev list and as a PR to bitcoin/bips.
3. Reviewers tear it apart: ambiguities, security concerns, edge cases, interaction with prior BIPs.
4. Once stable, the BIP editor merges it; it gets a number (BIP-341) and the status "draft" or "proposed".
5. Implementations land in Bitcoin Core / wallets / other clients. For consensus changes: activation parameters chosen.
6. After deployment + adoption, BIP-341 is promoted to "final"; deprecated proposals get "replaced" or "withdrawn".
WORKED_EXAMPLE
BIP-341 — quick reference card
EXAMPLE
BIP number : 341
Title : Taproot (BIP 341)
Area : Script
First published: 2020
Status : final
Fork class : soft
Motivation : unify single-sig + multi-sig + script-path spending in one tweaked-key output.
Mechanism : Taproot — P2TR output is a single 32-byte tweaked pubkey hiding a MAST tree.
Where it shows up : every "bc1p..." address; on-chain footprint identical to a single key.
Read the spec : https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki
KEY_PROPERTIES
OPT-IN
No authority can force a BIP on anyone. Adoption depends entirely on whether the change is genuinely useful.
NUMBERED
Stable numeric reference — BIP-341 means the same thing across every wallet, miner, and node that has read this spec.
BIP-341 is a soft fork — it changes (or proposes to change) the rules every full node enforces.
DEPLOYED
Implementations of BIP-341 are in production. The behaviour is observable on mainnet today.
COMMON_PITFALLS
Things that catch people out
PITFALLS
- BIP-341 is a soft fork — old clients accept new behaviour but don't enforce it. Validate against an upgraded node to be sure the rule is being checked.
- Don't confuse "draft" / "proposed" / "final" status — read the BIP header before relying on it in production.
- The BIP number is just an editorial counter — it doesn't imply correctness or stability. Always cross-reference with the latest bitcoin/bips repo.
RELATED_CONCEPTS
Other terms from Upgrades & BIPs — click any to read its page:
TERMINOLOGY_INDEX
TERMINOLOGY
Taproot (BIP 341)
The 2021 upgrade introducing key-aggregable Schnorr signatures and Merkleized script trees.
Segregated Witness (SegWit, BIP 141)
The 2017 upgrade separating witness-data/">witness data, fixing tx malleability, and introducing weight units.
Tapscript (BIP 342)
Script-language updates accompanying Taproot — new opcodes, removed limits.
Schnorr (BIP 340)
The Schnorr signature spec adopted by Taproot.
BIP Process
The community workflow for proposing, discussing, and tracking changes to Bitcoin.
Soft Fork Activation
MASF (Miner-Activated Soft Fork)
Activation triggered by miner signaling in block versions.
UASF (User-Activated Soft Fork)
Activation enforced by economic nodes regardless of miner signaling.