A concrete example
Two independent participants contribute shares without normally assembling a full key.
In context
A two-of-three arrangement can tolerate one unavailable participant, but availability alone says little about compromise resistance. Examine where shares are generated, which parties operate them, how devices authenticate, and whether one administrator controls multiple shares. Several machines in one administrative domain may not provide meaningful independence.
The related mechanism, visually
- 01Distributed shares
- 02Independent policy checks
- 03Threshold cooperation
- 04One verifiable signature
Read these as connected concepts, not necessarily consecutive steps.
Read the explanation
Threshold signing distributes secret material so a required subset can cooperate to produce a signature. Depending on the protocol, no single participant reconstructs the full private key during ordinary signing. The resulting signature may look like an ordinary single-key signature on-chain, so observers cannot infer the internal approval process from it.
Put the mechanism into context
A 2-of-3 design places two shares on servers managed by one administrator and the third with an independent team. Draw a participant map and an administrator map. Compare them rather than treating server count as a control count.
Apply it in the workshop →What this mechanism does not guarantee
Threshold security depends on implementation, share generation, communication and operational independence. Three shares in one compromised administrative domain may not provide three independent controls. Recovery, resharing, participant removal and audit evidence deserve the same attention as the normal signing demonstration.
Explore the full explanation
MPC wallets and threshold signing
Multi-party computation allows participants to calculate a result jointly without revealing their private inputs to one another.