A multi-signature system requires a transaction or message to carry signatures from multiple distinct public keys. Replacing Alice’s sole approval with n required signers means an attacker must compromise every signer to forge a valid transaction. section 8.8
Common design choices include:
- Use signature aggregation to compress several signatures into one and reduce transaction-size overhead; BLS signatures support this approach. section 8.8
- Use distributed key generation (DKG) to aggregate public keys while keeping the associated private key from ever existing in clear form. section 8.8
- Use threshold variants that accept signatures from only m of n participants. section 8.8
Shared approval for a financial transaction
A protocol initially accepts a transaction signed only by Alice. Requiring signatures from Alice and several other public keys distributes trust and removes Alice as the sole point of failure. section 8.8

