> For the complete documentation index, see [llms.txt](https://docs.vultisig.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vultisig.com/security-and-technology/difference-to-multi-sig.md).

# Vultisig vs Multisig

TSS vs on-chain multisig: no complete private key, works on Bitcoin, normal signature on-chain.

The main difference between Threshold Signature Schemes (TSS) and Multi-Signatures (MS) lies in their approach to generating signatures. In TSS, the signature is created by combining vault shares using Zero-Knowledge Proofs—no single private key is ever constructed. In contrast, MS involves multiple private keys, each contributing to the final signature.

***

## Visualization: Threshold Signatures

<div align="center"><figure><picture><source srcset="/files/SpCVG9FDIpiA0S05y6w4" media="(prefers-color-scheme: dark)"><img src="https://644481292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfSRUQVZENEfvoqS6R0GO%2Fuploads%2Fgit-blob-bca285efbc980a5001592b0d7f4a1ea7049f11e3%2FTX%20black.png?alt=media" alt="" width="375"></picture><figcaption><p><strong>Threshold Signatures</strong></p></figcaption></figure></div>

## Visualization: Multi-Signatures

<figure><picture><source srcset="/files/3RW4T26lVXcTcx5XY73u" media="(prefers-color-scheme: dark)"><img src="https://644481292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfSRUQVZENEfvoqS6R0GO%2Fuploads%2Fgit-blob-33a5b600834c30454a5bbcca4802c5845831d170%2FMS%20dark.png?alt=media" alt="" width="375"></picture><figcaption><p><strong>Multi-Signatures</strong></p></figcaption></figure>

***

## Comparison

| Factor                  | Threshold Signature Scheme                            | Multi-Signature                       |
| ----------------------- | ----------------------------------------------------- | ------------------------------------- |
| **Private Key Storage** | No private key constructed; uses vault shares and ZKP | Multiple private keys held by parties |
| **On-Chain Footprint**  | Single signature on-chain                             | Multiple signatures visible on-chain  |
| **Redundancy**          | High; lost shares can be re-shared                    | Low; lost keys require fund migration |
| **Compatibility**       | Multi-chain: ECDSA and EdDSA                          | Single chain support                  |
| **Flexibility**         | Adjustable thresholds, replaceable devices            | Fixed once created                    |
| **Adding Participants** | Supported                                             | Not supported                         |

***

## Key Advantages of TSS

### No Key Reconstruction

In TSS, the private key never exists in one place. Multi-sig requires each signer to hold a complete private key, creating multiple single points of failure.

### Chain Agnostic

TSS works identically across all blockchains that support standard signatures. Multi-sig implementations vary by chain and often aren't available.

### Lower Fees

TSS produces a single signature regardless of threshold. Multi-sig requires multiple on-chain signatures, increasing transaction fees.

### Better Privacy

TSS transactions appear identical to normal single-signature transactions. Multi-sig transactions expose the signing structure on-chain.

### Flexibility

TSS allows resharing to add/remove devices without changing addresses. Multi-sig typically requires fund migration for any configuration change.

***

## Conclusion

Flexibility and security advantages make TSS the superior approach for managing digital assets compared to traditional multi-signature schemes.

***

## Related

* [How DKLS23 Works](/security-and-technology/how-dkls23-works.md)
* [TSS Actions](/security-and-technology/tss-actions.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vultisig.com/security-and-technology/difference-to-multi-sig.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.