Threshold Schemes in Blockchains and HSMs

Bitcoin and Ethereum support on-chain multi-signature scripts (P2MS/P2SH/multisig in Solidity). These require t-of-n public keys to co-sign a transaction, verified by the blockchain. The structure is public and transparent: anyone can see that the address requires multiple signers. Threshold ECDSA produces a standard single-key address and a standard single signature, making threshold structure completely invisible on-chain.

Threshold ECDSA advantages over on-chain multi-sig: a single transaction signature (lower gas fees), no multi-sig policy visible on-chain (privacy), compatible with any blockchain that uses ECDSA (including chains without native multi-sig support), and key rotation without changing the blockchain address (since the public key stays the same after a key refresh). These advantages make threshold ECDSA the preferred approach for institutional custody.

Fireblocks is the largest institutional MPC custody provider. Their architecture uses 2-of-3 threshold ECDSA: two shares reside in Fireblocks infrastructure (one in SGX, one in cold storage) and one share resides with the customer. A transaction requires cooperation from at least two of the three shares. No single party (including Fireblocks) can unilaterally move funds. Over $4 trillion in transactions have been processed through this system.

Qredo Network uses threshold ECDSA with a Layer 2 network for enterprise custody and trading. Coinbase Prime uses MPC-based custody built on threshold ECDSA (using tss-lib) to secure institutional client assets. Both systems distribute key shares across geographically separated data centers with HSMs protecting individual shares. Copper.co similarly offers MPC custody with SGX-protected key shares.

Anchorage Digital is a federally chartered digital asset bank using MPC-based threshold signatures for custody. Their key management architecture distributes shares across multiple data centers and uses biometric authentication to authorize signing ceremonies. The system is designed to meet federal banking regulations for key management while eliminating the traditional single-HSM custody model.

The DNSSEC root zone Key Signing Key (KSK) ceremony is the most public example of threshold key management for critical infrastructure. Conducted quarterly, the ceremony requires 7 of 14 Crypto Officers from around the world to be physically present at one of two secure facilities. Each officer holds a smart card containing a key share. Multiple hardware security modules verify the quorum before allowing the KSK to sign the root zone.

Hardware Security Modules (HSMs) can split private keys using M-of-N key splitting (based on Shamir's Secret Sharing). AWS CloudHSM clusters synchronize key material across multiple HSMs in a cluster. Thales Luna HSMs support "split knowledge" key ceremonies where multiple operators provide key components that are combined only within the tamper-resistant hardware. This prevents any single administrator from extracting key material.

AWS CloudHSM provides a cluster of HSMs that synchronize automatically. When a key is created in one HSM, it is replicated to all cluster members. The cluster presents a single logical HSM to applications but provides hardware redundancy. For regulatory compliance (PCI-DSS, HIPAA), using an HSM cluster rather than software key storage provides the tamper-evident and tamper-resistant protections required by auditors.

Unbound Key Control (UKC, now part of Dynatrace) implements virtual HSM using threshold ECDSA. Instead of a physical HSM, the key material is split across multiple servers using threshold cryptography. Operations are performed without reconstructing the key. This "software HSM" approach provides HSM-equivalent security without the hardware cost and complexity, while enabling cloud-native deployment and elastic scaling.

Beyond key management, quorum-based systems require approval from t-of-n authorized parties before executing sensitive operations. AWS Systems Manager Change Manager, HashiCorp Vault with Shamir Unseal, and CyberArk Privileged Access all implement quorum policies. These systems ensure that no single administrator can perform destructive operations unilaterally, providing defense against insider threats and compromised credentials.

Thales Luna Network HSMs support Threshold Key Management for high-security environments. Luna HSMs can implement m-of-n key custodian schemes for key generation ceremonies. The key material never leaves the HSM in plaintext; instead, wrapped shares are distributed to custodians and can only be re-combined inside an HSM. This is widely used for certificate authority key ceremonies in PKI infrastructure.

What is the primary on-chain advantage of threshold ECDSA over Bitcoin/Ethereum native multisig?

Threshold ECDSA outperforms on-chain multi-sig by producing standard single-key addresses and signatures. Fireblocks, Qredo, and Coinbase use it to secure institutional assets. DNSSEC root KSK ceremonies use hardware-enforced quorum. AWS CloudHSM clusters synchronize key material across hardware. Unbound Key Control virtualizes HSMs using threshold cryptography. Quorum-based access control extends threshold principles to administrative operations.