This guide explains BIP 340 Schnorr signatures in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 340 specifies a 64-byte Schnorr signature scheme for the secp256k1 curve used by Bitcoin. Its BIP record is Deployed, reflecting its use with Taproot, but the document is a precise cryptographic standard rather than a generic licence to substitute Schnorr signatures into every protocol.
- Why it matters: BIP 340 standardises an exact Schnorr scheme for Bitcoin’s curve and is now Deployed. Its benefits come from disciplined implementation, not from the Schnorr name alone: encodings, tags, nonces and tests are all consensus-critical.
- Current position: Its BIP record is Deployed, reflecting its use with Taproot, but the document is a precise cryptographic standard rather than a generic licence to substitute Schnorr signatures into every protocol.
BIP 340 Schnorr signatures in simple English
BIP 340 Schnorr signatures: Schnorr linearity enables efficient multisignature and threshold constructions, adaptor signatures and related protocols. Secure aggregation requires a separately reviewed protocol.
Simple example
A node operator is checking BIP 340 Schnorr signatures. Signatures are 64 bytes and public keys are 32-byte x coordinates. The BIP is a Deployed specification assigned on 19 January 2020.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Taproot:
- A Bitcoin upgrade that added new signature and script options for spending outputs.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Status and scope
The BIP is a Deployed specification assigned on 19 January 2020. Historical publication can explain the proposal as introduced while a present-day note identifies the later deployment without rewriting the chronology.
Fixed encodings
Signatures are 64 bytes and public keys are 32-byte x coordinates. The scheme selects curve points with even y coordinates, so parsers must enforce the exact range and point-lifting rules.
Security properties
The design targets strong unforgeability and avoids ECDSA-style inherent signature malleability. Those properties still depend on correct hashing, scalar arithmetic, key handling and protocol context.
Linearity and applications
Schnorr linearity enables efficient multisignature and threshold constructions, adaptor signatures and related protocols. Secure aggregation requires a separately reviewed protocol; naively adding keys or signatures can be unsafe.
Tagged hashing
BIP 340 prefixes hashes with a context-specific tag construction to separate nonce, challenge and auxiliary-data domains. Implementations must not replace tags or field order with an equivalent-looking custom format.
Nonce discipline
Nonce generation incorporates the secret key, message and optional auxiliary randomness. Reuse or biased custom generation can expose the private key, so use reviewed libraries and the supplied vectors.
How specialists test it
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
Frequently asked questions
What is the main point of BIP 340 Schnorr signatures?
BIP 340 Schnorr signatures: Schnorr linearity enables efficient multisignature and threshold constructions, adaptor signatures and related protocols.
For BIP 340 Schnorr signatures, what should a beginner know about status and scope?
The BIP is a Deployed specification assigned on 19 January 2020. Historical publication can explain the proposal as introduced while a present-day note identifies the later deployment without rewriting the chronology.
For BIP 340 Schnorr signatures, what should a beginner know about fixed encodings?
Signatures are 64 bytes and public keys are 32-byte x coordinates.
For BIP 340 Schnorr signatures, what should a beginner know about security properties?
The design targets strong unforgeability and avoids ECDSA-style inherent signature malleability.
Conclusion
BIP 340 standardises an exact Schnorr scheme for Bitcoin’s curve and is now Deployed. Its benefits come from disciplined implementation, not from the Schnorr name alone: encodings, tags, nonces and tests are all consensus-critical.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.