Why it exists
BIP 340 specifies the Schnorr signature scheme used by Taproot. A signature demonstrates authorization by a private key for a particular message; verification uses the corresponding public key. The standard fixes the exact encoding and verification rules so independent implementations reach the same answer.
How it works
The scheme uses Bitcoin’s secp256k1 curve, 32-byte x-only public keys and 64-byte signatures. Its challenge calculation commits to the public key as well as the nonce point and message. Tagged hashes separate different cryptographic uses so the same data is not accidentally interpreted in another context.
The signer combines a fresh secret nonce with the private key and message-dependent challenge. The verifier checks the resulting curve relationship. BIP 340 defines this primitive; BIP 341 defines the transaction message and Taproot spending rules that put it to work on Bitcoin. Multi-party signing requires an additional protocol such as MuSig2.
A practical example
A wallet approves a Taproot payment to one recipient. If the transaction’s committed destination or amount changes afterwards, the message being checked changes and the signature will not validate for that altered transaction. This is why the signer must first display the right payment: cryptography protects the approved message, not a user’s unexpressed intention.
What to keep in mind
Schnorr signatures do not encrypt a transaction or make its amounts private. They also do not automatically turn separate keys into a threshold wallet. Nonce generation is security-critical; reusing or leaking a secret nonce can expose the private key.
Status & implementation
Bitcoin Core implements Schnorr validation as part of Taproot. Core’s implementation inventory distinguishes the original validation implementation from mainnet activation support in 0.21.1.
Specification status: Deployed · Sources checked 13 November 2026
