The whole difference is one missing division.
s·G = R + e·P
Bitcoin shipped in 2009 with the second-best signature scheme, and it was not a mistake someone made — it was a patent. Claus Schnorr held US patent 4,995,082 over the scheme that now carries his name, and it did not expire until February 2008, a few months before the whitepaper appeared. So Satoshi used ECDSA, the unencumbered standard, and the network spent twelve years paying for that choice in bytes and in privacy. Then, in November 2021, at block 709,632, Bitcoin quietly switched to Schnorr for everything new.
The thing that makes Schnorr different from ECDSA is one word: linearity. And it is the kind of property that sounds like a math footnote and turns out to rewrite what a wallet can do.

Two Analogies That Actually Hold
Here are the two analogies I keep coming back to, because each one explains a different half of what “linear” buys you.
The paper shredder versus the seal. ECDSA’s signature is like a paper shredder: it mangles the message and the key into an output you cannot reverse, and two shreddings cannot be recombined into one. Schnorr’s signature is like a wax seal on a chain of custody — the pieces stay algebraically whole, so two seals on the same document can be pressed together into one seal for the two signers combined. Nothing about the message is hidden either way; the difference is what you can do with the signature afterward.
The invoice versus the itemized bill. A 2-of-3 multisig spent the old way publishes two signatures and three public keys, every time, forever. That is an itemized bill for your security policy. Spent the Schnorr way, it publishes one signature against one key — an invoice, with no line items. Both settle the same debt. One of them tells the whole room how many people were involved.
verification: s·G = R + e·P · where e = hash(R‖P‖m) · because s = k + e·d and R = k·G
Where the Linearity Comes From
The whole difference reduces to a single missing operation. ECDSA’s signing step requires a modular inverse — a division, essentially — and that inverse is what breaks the linearity. Schnorr’s signing step is pure addition and multiplication:
# signing with private key d, secret nonce k
R = k * G
e = hash(R || P || m) # the challenge, computed via Fiat-Shamir
s = k + e * d # just addition and multiplication
signature = (R, s) # 64 bytes total
Because there is no division, the signature is a linear function of the private key. Add two private keys, and the sum signs for the sum of the public keys. The verification equation s·G = R + e·P is the same arithmetic rearranged.
The practical payoffs are three, and they stack:
64 / 32 / 2–3× —
bytes in a Schnorr signature · bytes in an x-only public key · batch-verification speedup a node can get
- Key aggregation. A group of signers can hold one apparent public key between them, and produce one signature that verifies against it. On chain, a fifteen-signer arrangement is indistinguishable from a single wallet.
- Batch verification. Because the equation is linear, a node can combine hundreds of signatures into one multi-scalar multiplication and check them together, with random coefficients to stop one invalid signature from masking another.
- Non-malleability. ECDSA signatures can be transformed into other, equally-valid signatures for the same message — a nuisance for every higher-layer protocol. Schnorr is non-malleable by construction.
| ECDSA | Schnorr (BIP-340) | |
|---|---|---|
| Signature size | 71–72 bytes, DER-encoded, variable | 64 bytes, fixed |
| Public key | 33 bytes compressed (or 65 uncompressed) | 32 bytes, x-only |
| Combine signatures | not possible | linear, adds up |
| Batch verify | no | yes, ~2–3× speedup |
| Malleable | yes | no, by construction |
| In Bitcoin since | 2009 | block 709,632 (Nov 2021) |

The Two Footguns the Spec Exists to Prevent
The reason Schnorr needs a formal BIP at all is that “just do the math” is not a signature scheme — it is a consensus split waiting to happen. BIP-340 pins down two things that would otherwise bite.
Key prefixing. The challenge e hashes R, the public key P, and the message together. That seems redundant until you realize it blocks related-key attacks: without the public key in the hash, a signature valid for one key can sometimes be repurposed against another. Including P is what makes key aggregation and the Taproot tweak safe.
Tagged hashes. Every hash inside the scheme is prefixed with a domain string — BIP0340/challenge, BIP0340/nonce, and so on. A hash computed for a signature challenge can never be mistaken for one computed for something else that happens to hash similar bytes. That is domain separation, and it is the kind of thing that only matters in the bug you never ship.
And the nonce is still the sharp edge, exactly as it was in the ECDSA piece. Reuse k across two messages and the private key falls out of simple subtraction. BIP-340’s answer is a deterministic nonce derived from the key and message, XORed with fresh auxiliary randomness — safe even on hardware with a mediocre random number generator.
What It Costs You to Keep Using ECDSA
None of this changes the fact that most bitcoin still sits in pre-Taproot outputs, and every one of those spends uses ECDSA. The two schemes live side by side, and the cost of staying old is measurable:

- You pay the itemized bill. Every legacy multisig spend publishes every key and every signature. The fee difference compounds across the consolidations long-term holders inevitably do.
- You keep the tell. Chain-analysis firms classify addresses by shape, and multisig has always been a loud shape. Protecting yourself properly used to announce that you had something worth protecting.
- You miss the batch discount. Nodes verifying your blocks do not get the ~2–3× speedup Schnorr enables during initial block download, which is a network-wide cost, not just yours.
The honest summary for a single-key holder is that the switch is a rounding error — one signature gets a few bytes smaller, and that is about it. The payoff is for anyone doing multisig, Lightning, or Taproot, and it is not a fee optimization. It is that the shape of your spending stops revealing how many people signed it.
(The End)


