Technical definition
In cryptography, a trusted setup refers to a multi-party computation (MPC) where one or more parties generate secret random values (often called "toxic waste") that are used to create public parameters (e.g., structured reference strings like CRS or SRS). These secret values must be destroyed or kept private to ensure the security of the system, as knowledge of these values could allow an attacker to forge proofs or break the cryptographic scheme. The process is 'trusted' because if any participant misbehaves by keeping or leaking their secret values, the entire system's security is compromised.
An analogy
Imagine a group of scientists creating a master key for a city’s vault. Each scientist contributes a piece of the key, and then they all destroy their individual pieces. If even one scientist secretly kept a piece, they could later unlock the vault alone. The trusted setup ensures everyone follows the rules and destroys their pieces to keep the vault secure.
Why it matters
Trusted setups are critical for enabling advanced cryptographic primitives like zk-SNARKs (used in privacy-preserving blockchains) or secure multi-party computation. Without them, these systems would either be insecure or require impractical assumptions about hardware or software trust.
Where it came from
The concept emerged with the introduction of zk-SNARKs in the early 2010s, notably in the Zerocash protocol (2013) and later in Zcash (2016). Early implementations relied on a single trusted party (e.g., a ceremony with scientists), which was later replaced by multi-party ceremonies (e.g., Zcash’s Powers of Tau ceremony in 2018) to distribute trust.
Example in practice
In Zcash, a trusted setup was used to generate the public parameters for its zk-SNARKs, enabling private transactions on its blockchain. The ceremony involved hundreds of participants worldwide, each contributing randomness to the setup, which was then combined and partially destroyed to ensure no single party could compromise the system.
Common misconceptions
- Trusted setups are always insecure → Correction: While they require trust, modern multi-party ceremonies (e.g., Powers of Tau) distribute this trust across many participants, reducing risk.
- The setup must be done by a single trusted entity → Correction: Many modern systems use distributed ceremonies where no single entity holds all the secrets.
- Once completed, the setup can never be reused → Correction: Some setups (e.g., universal CRS) can be reused for multiple applications, though others are application-specific.
Risks & limitations
- Single-point-of-failure: If a single participant in a trusted setup ceremony is compromised or malicious, the entire system’s security may be at risk.
- Lack of verifiability: In some setups, it may be impossible to prove that secrets were truly destroyed, leaving residual trust assumptions.
- Complexity: Trusted setups are technically complex and require careful execution; errors can lead to vulnerabilities.
- Centralization risks: Even distributed ceremonies may rely on a small group of coordinators, which could become a target for coercion or infiltration.