A laptop, transaction receipt and hourglass for investigating a delayed payment, editorial illustration
BIP 341 / TRANSACTIONS

Taproot spending rules.

Taproot combines a key-spend path with the ability to commit to alternative script conditions.

Read the explanation
← All standards

Why it exists

BIP 341 defines Taproot outputs and their spending rules. It combines an ordinary-looking public-key spending path with a commitment to optional alternative scripts. A wallet can use the cooperative path without publishing every contingency it prepared when receiving the funds.

How it works

A Taproot output contains a tweaked public key derived from an internal key and, when present, a script-tree commitment. A key-path spend supplies an appropriate Schnorr signature. A script-path spend reveals the chosen script, the information needed to execute it, and a control block proving that script belongs to the committed tree.

The other scripts do not have to be revealed. BIP 341 also defines what Taproot transaction signatures commit to, including rules for different signature-hash modes. BIP 342 supplies the execution rules for Tapscript leaves, while address encoding and common account derivation are separate standards.

PUT IT IN CONTEXT

A practical example

A shared wallet might use a cooperative aggregate key for everyday spending and include a delayed recovery script as an alternative. If everyone cooperates, the on-chain spend can use the key path. If recovery is needed, the spender reveals that particular recovery leaf and satisfies it. The leaf cannot be invented after funding; it must match the original output commitment.

What to keep in mind

Outputs and amounts remain public. Script-path spending reveals the selected conditions, and wallets still need to preserve enough policy information to recover. Losing a script tree or derivation details can matter even when a seed survives. Taproot alone does not supply a complete inheritance or multisig protocol.

Status & implementation

Taproot is an activated Bitcoin consensus upgrade. Bitcoin Core’s implementation inventory records BIPs 340–342 together, with mainnet activation support in 0.21.1.

Specification status: Deployed · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close