Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 44 of 189

ECDSA vs EdDSA vs BLS

The three signature schemes you'll meet across the crypto stack — what each does well, what tradeoffs they impose, and why Ethereum uses three of them simultaneously.

Beginner
8 min readUpdated November 2026Block Clarity Hub Editorial Team

The basics

Why Three Schemes?

Almost every cryptocurrency transaction is authorised by a digital signature. The math behind that signature can use different schemes, each with its own performance, security, and feature profile. The three you'll meet most often are ECDSA (Bitcoin, Ethereum's externally-owned accounts), EdDSA (Solana, Cardano, many newer chains), and BLS (Ethereum's consensus layer, Filecoin, Chia). Knowing the difference helps you understand why some chains can aggregate millions of signatures into one and others can't.

ECDSA — The Bitcoin Original

ECDSA (Elliptic Curve Digital Signature Algorithm) on the secp256k1 curve is what Bitcoin chose in 2009 and what every EOA on Ethereum still uses. It's well-understood, widely deployed in hardware and supported by most wallets and libraries. The catch: it requires good randomness during signing (a deterministic variant, RFC 6979, fixes this), can't aggregate easily, and verification is moderately expensive.

EdDSA — Cleaner and Deterministic

EdDSA (Edwards-curve Digital Signature Algorithm) on Ed25519 was designed in 2011 to fix ECDSA's footguns. Signing is deterministic by default (no randomness needed, so no risk of leaking the key via bad RNG), verification is faster, and the API is simpler. Solana, Cardano, Stellar and Near use it, as do many other newer chains. The catch: it doesn't aggregate well either, and it's less universally supported by old hardware.

  • ECDSA (secp256k1): Bitcoin, Ethereum EOAs, classic web crypto
  • EdDSA (Ed25519): Solana, Cardano, Stellar, Near, modern wallets
  • BLS (BLS12-381): Ethereum consensus, Filecoin, Chia, threshold protocols
  • All three give you 'I have the key, here's a signature' — the differences are about cost, determinism, and aggregation

Key Takeaways

  • Three dominant schemes: ECDSA (Bitcoin/ETH-EOAs), EdDSA (many newer chains), BLS (consensus + aggregation)
  • ECDSA needs careful randomness; EdDSA is deterministic by design
  • BLS uniquely allows aggregating many signatures into one — critical for Ethereum's very large validator set
  • You'll see all three in production crypto code; they're not competing, they fit different niches

Going deeper

BLS — The Aggregation Superpower

BLS (Boneh-Lynn-Shacham) signatures have one defining feature no other scheme matches: any number of signatures over different messages, from different signers, can be combined into a single signature that verifies for the union. This is what lets Ethereum's beacon chain process attestations from hundreds of thousands of validators — each validator attests once per epoch, in a committee assigned to a single slot, so only a subset of validators attests in any given slot — and they're all BLS-aggregated. Without aggregation, the consensus layer would be impossible at Ethereum's validator scale.

Verification Cost Comparison

Ed25519 verification is cheap and batchable (the original paper reports 273,364 CPU cycles per verification on a 2010-era Intel CPU, and less per signature in batches). A single BLS12-381 verification needs two pairings, so it is slower than ECDSA or Ed25519 individually. The saving comes from aggregation: n signatures on the same message (such as the attestations from one Ethereum committee) are checked against one aggregated public key with two pairings, and n signatures on different messages need n+1 pairings instead of 2n. This makes BLS much cheaper at scale despite being slower per signature.

Why Bitcoin Stuck With ECDSA

Bitcoin's Taproot upgrade (2021) added Schnorr signatures alongside ECDSA on the same secp256k1 curve. Schnorr enables multi-sig aggregation (multiple signers, one signature for the same message), which is useful for Lightning and CoinJoin but isn't full BLS-style aggregation. Bitcoin chose Schnorr partly because it's much closer to the existing infrastructure than BLS — same curve, same hardware path, simpler migration. It's a pragmatic middle ground.

Ethereum's Two-Curve Reality

Ethereum currently uses ECDSA secp256k1 for execution-layer transactions (every EOA) and BLS12-381 for consensus-layer attestations. Smart-contract wallets (ERC-4337) can also verify passkey-style secp256r1 (P-256) signatures, and the Fusaka upgrade added a native secp256r1 precompile (EIP-7951). One chain, three signature schemes coexisting — a transitional state that may simplify over years.

Key Takeaways

  • BLS uniquely enables aggregation across signers and messages — the killer feature for consensus protocols
  • Verification: Ed25519 and ECDSA are cheap per signature, BLS wins at scale via aggregation
  • Bitcoin's Schnorr (Taproot) gives partial aggregation without full BLS
  • Ethereum already runs three schemes side by side: ECDSA execution, BLS consensus, secp256r1 for passkey 4337 wallets

Under the hood

Pairing-Based Cryptography Under BLS

BLS relies on elliptic-curve pairings — bilinear maps between two groups that let you check equations like e(g1, g2) = e(g3, g4) without solving the discrete log. This pairing operation is what enables signature aggregation: verifying an aggregated BLS signature is a pairing check, not N individual scalar multiplications. The BLS12-381 curve was specifically engineered for efficient pairings; it's used in Ethereum, Filecoin, Zcash Sapling, and a number of ZK systems.

Rogue Public Key Attacks and Proofs of Possession

Naive BLS aggregation has a subtle attack: a malicious participant can register a 'rogue' public key derived from existing keys, then forge an aggregate that incriminates honest signers. The defence is requiring every registered public key to come with a 'proof of possession' (PoP) — a signature on the public key itself, which only the holder of the private key can produce. Ethereum's consensus layer enforces this by checking a BLS signature over each deposit's data (the deposit contract itself does not). Skip the PoP and your aggregation scheme is broken.

Post-Quantum Considerations

ECDSA, EdDSA, and BLS all rely on the elliptic-curve discrete log problem — broken by Shor's algorithm on a sufficiently large quantum computer. None of them are post-quantum secure. NIST has already standardised quantum-resistant signatures — ML-DSA (FIPS 204, derived from CRYSTALS-Dilithium) and SLH-DSA (FIPS 205, derived from SPHINCS+) — and is developing a further standard derived from FALCON. NIST IR 8547 says quantum-vulnerable signature algorithms such as ECDSA and EdDSA will be deprecated after 2030 and disallowed after 2035, so the migration is a multi-year programme that is already under way.

Schnorr in the Mix

Schnorr signatures are sometimes presented as an alternative to ECDSA. They're closely related — both rely on the same discrete log assumption — but Schnorr is linear (signatures and keys can be added), while ECDSA is non-linear. Bitcoin's Taproot enables Schnorr; this makes Lightning channel opens, multi-sig setups, and various advanced protocols dramatically more efficient and private. Schnorr is not BLS — it doesn't aggregate across different messages — but it's a major upgrade from ECDSA in its niche.

Hardware Wallets and Signature Schemes

Hardware wallets (Ledger, Trezor) traditionally support ECDSA secp256k1 and Ed25519 well. BLS is a different, pairing-based operation, so check whether a particular device and app support it before relying on it.

Key Takeaways

  • BLS aggregation depends on elliptic-curve pairings on BLS12-381 — a specialised curve choice
  • Naive BLS aggregation is vulnerable to rogue-key attacks; proofs of possession defend against them
  • All three schemes are post-quantum vulnerable; NIST's timeline deprecates ECDSA and EdDSA after 2030 and disallows them after 2035
  • Schnorr (Taproot) is a partial upgrade from ECDSA enabling key/signature additivity without full BLS
  • Check hardware-wallet support before relying on BLS; ECDSA and Ed25519 are the widely supported schemes

Related Content

Account Abstraction (ERC-4337)

How ERC-4337 brings smart-contract wallets, social recovery, gasless transactions, and arbitrary signature schemes to Ethereum without changing the protocol — and why every wallet UX of the next decade will use it.

Data Availability Sampling

How light nodes can be cryptographically confident that a block's full data was published — without downloading it — and why this is the key unlock for Ethereum's full danksharding and the modular blockchain stack.

Finality and Fork Handling

What it means for a transaction to be 'final,' why different chains finalise differently, how reorgs happen, and the MEV incentives that complicate the picture.

State Pruning and Expiry

Why Ethereum's node storage needs have grown to terabytes, what 'archive,' 'full,' and 'light' nodes actually store, and how proposals like EIP-4444 and new state-tree designs (verkle or binary) aim to keep node hardware accessible for years to come.

zk-SNARK vs zk-STARK vs PLONK

How the three major proof-system families compare on trusted setup, proof size, prover cost, and quantum resistance — and which production rollups picked which.

Threshold Signatures and MPC

How t-of-n threshold signatures and multi-party computation let multiple parties sign together without any one holding the full key — the cryptography behind Fireblocks and modern institutional custody.

Verifiable Random Functions

How VRFs produce randomness that's both unpredictable before commitment and cryptographically verifiable after — enabling fair lotteries, leader election, and on-chain randomness without trusted parties.

Hash Functions Compared

SHA-256, Keccak-256, Blake3, and Poseidon — which one each chain uses, why ZK systems needed a new family of 'arithmetic-friendly' hashes, and what tradeoffs each makes.

References & further reading