# Multisignature

In cryptocurrencies, multisig feature allows you to sign a transaction with more than one private key. Funds protected with multisig can only be spent by signing with M-of-N keys.

| **Use Case**                                                            | **Scheme** | **Example**                                                                                                                                        |
| ----------------------------------------------------------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Shared Account                                                          | (1-of-2)   | Both husband and wife individually have full access to their funds.                                                                                |
| [Consensus Account](/wallets/guides/multisig/2-2-multisig.md)           | (2-of-2)   | Both husband and wife must agree to spend their funds.                                                                                             |
| [Threshold account](/wallets/guides/multisig/2-3-multisig.md)           | (2-of-3)   | An escrow service is involved as an independent 3rd party, to co-sign with either the seller, or with the buyer, if seller and buyer do not agree. |
| [Secure account](/wallets/guides/multisig/2-3-multisig.md)              | (2-of-3)   | A single owner controls all 3 keys but secures them via a different means to diversify risks.                                                      |
| [Arbitrary threshold account](/wallets/guides/multisig/m-n-multisig.md) | (M-of-N)   | Some cryptocurrencies provide full flexibility on the number of signers.                                                                           |

### Beldex Multisignature <a href="#beldex-multisignature" id="beldex-multisignature"></a>

Beldex doesn't directly implement multisignatures (at least not in a classical sense). Monero emulates the feature by secret splitting and Beldex has brought this code from Moneros code base.

Transactions are still signed with a single spend key. The spend key is a sum of all N private keys. The rationale for such design is to decouple multisig from ring signatures.

Let's consider the 2-of-3 scheme. We have 3 participants. Each participant is granted exactly 2 private keys in a way that pairs do not repeat between participants. This way any 2 participants together have all 3 private keys required to create the private spend key.

Multi-signing is a wallet-level feature. There is no way to learn from the blockchain which transactions were created using multiple signatures.

It is also worth noting in Beldex there is no multisig addresses as such. The Address structure does not care how the underlying private spend key got created.

In Beldex, multisignature is supported for M of N participants making any combination of signers possible.

After multisig wallet setup every participant ends up knowing the public address and private view key. This is necessary for participants to recognize and decipher transactions they are supposed to co-sign.

### Guides <a href="#guides" id="guides"></a>

| Guide                                                                          | Description                               |
| ------------------------------------------------------------------------------ | ----------------------------------------- |
| [2-of-2 Multisigniture Wallet Setup](/wallets/guides/multisig/2-2-multisig.md) | Setup Guide for a 2 of 2 Multsig Wallet.  |
| [2-of-3 Multisigniture Wallet Setup](/wallets/guides/multisig/2-3-multisig.md) | Setup Guide for a 2 of 3 Multsig Wallet.  |
| [M-of-N Multisig Setup Guide](/wallets/guides/multisig/m-n-multisig.md)        | Setup Guide for a M of N Multisig Wallet. |


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.beldex.io/wallets/multisignature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.