Bitcoin VerityOpen comparator

Level 9 · Advanced technical layer

Schnorr signatures and Taproot

How BIP 340 signatures support Taproot and why key aggregation is a separate protocol.

Article
89
Reading time
16 minutes
Reviewed
10 September 2026

In a nutshell

BIP 340 standardised 64-byte Schnorr signatures over secp256k1. Taproot commits to an internal key and optionally a script tree, allowing either a key-path signature or revelation of only the executed script branch.

01

What Schnorr changes

Schnorr verification has a linear algebraic form and supports batch verification and carefully designed multisignature protocols. Its security still depends on sound nonce generation and the exact BIP 340 encoding.

02

Aggregation needs a protocol

Adding public keys or partial signatures naively can enable rogue-key or nonce attacks. MuSig-style coordination adds coefficient, nonce and transcript rules; a Taproot key does not prove that multiple people created it.

03

Taproot commits to key and tree

BIP 341 tweaks an internal public key with a commitment to an optional Merkle tree. The resulting P2TR output looks the same on chain until spent and can use a single key-path signature when participants cooperate.

04

Privacy is conditional

A script-path spend reveals the chosen leaf and Merkle proof, not every unused branch. That can save data and hide alternatives, but transaction amounts, timing and input links remain public; Taproot is not automatic anonymity.

Level 9 · Advanced technical layer

Terms to know

Schnorr signature
The BIP 340 signature scheme used by Taproot.
Internal key
The key tweaked with the script-tree commitment to form a P2TR output.
Key path
Spending a Taproot output with a signature for its tweaked output key.

Common misconception

Schnorr automatically turns any group of keys into safe multisig.

A more accurate explanation

Secure key aggregation requires a dedicated protocol with rogue-key and nonce protections; the signature format alone is insufficient.

A more accurate explanation

Does Taproot make every payment private?

It can make cooperative and complex policies more uniform and reveal fewer branches, but public amounts and transaction-graph clues remain.

89

Key takeaways

  1. 01BIP 340 defines Bitcoin's Schnorr format.
  2. 02Key aggregation is a separate protocol.
  3. 03Taproot offers key and script paths.
  4. 04Only the used script branch is revealed.

A child-friendly recap

In very simple terms

Taproot can offer a simple signature opening plus hidden emergency rules. If one emergency branch is used, the others usually do not have to be revealed.

Reviewed: 10 September 2026

Sources and further reading

Sources support particular facts and definitions; listing one does not mean the editors endorse every view of its author.

01
BIP 340: Schnorr signaturesBitcoin Improvement Proposals
bips.dev
02
BIP 341: TaprootBitcoin Improvement Proposals
bips.dev
03
BIP 386: tr() descriptorsBitcoin Improvement Proposals
bips.dev

Educational material, not an investment recommendation.