<commit_before>---
title: 'Multisig Contracts'
taxonomy:
    category:
        - docs
---

*NEM team with like to thank the following contributors:*   
*Blog by Aenima (Telegram: @Aenima86)*    
*Video by TongoKong (Telegram: @tongokongo)*

##Introduction
This tutorial will teach you about:    
 - What are multi-signature contracts and accounts   
 - What is the typical use case   
 - How to create & edit these contracts   
 - How to send XEM from a multi-signature account.  
 
## What is a multi-signature contract 
NEM's multi-signature contracts work out of the box, ready to go with a push of a button and are universal, meaning they are built **into** the platform of the blockchain, not on top of the blockchain as in third-party reliant software for Bitcoin’s multisig. This unlocks various advantages and interesting possibilities for the user. But let’s first take a look at what a multi-signature contract is. The contract enables several people to administrate the activity of an account, control assets such as XEM from one account, other mosaics, or create additional contracts like when creating a new token. NEM’s multi-signature makes a contract that assigns rights and powers of a certain account to other accounts; this contract can be edited to suit most any needs. The contract converts a chosen regular account to a special multi-signature account. Now, this account cannot send funds on its own but is bound by the contract and administered accordingly to the contract via designated affiliated persons, i.e., cosigners. 
 
To illustrate this concept, take a look at Figure 1. Hannah has a NanoWallet account, and John has a NanoWallet account, but due to a multi-signature contract they also have accesses to a multi-signature account and can both use the funds in this account. The contract can be formed in a way such that **either** Hannah or John can separately use funds from the multi-signature account, i.e., "multi-user account", or that they **both** need to approve a transaction, i.e., "multisig account".
 
![Figure 1](http://i.imgur.com/UrE9Epm.png)
 
## What is the typical use case 
As you might already have discovered there can be a broad range of useful applications for multi-signature contracts and accounts. But let us take a look at some of the common use cases. The first use case is illustrated in Figure 2. Jonathan and Merryann live together, they have their own separate accounts, but they also need a shared account so that if Jonathan is out shopping, he can buy groceries for both him and Merryann. 
 
![Figure 2](http://i.imgur.com/yqr8xEv.png)
 <commit_msg>(Grav GitSync) Automatic Commit from saul<commit_after>---
title: 'Create Multisig Account'
taxonomy:
    category:
        - docs
---

*NEM team with like to thank the following contributors:*   
*Blog by Aenima (Telegram: @Aenima86)*    
*Video by TongoKong (Telegram: @tongokongo)*

##Introduction
This tutorial will teach you about:    
 - What are multi-signature contracts and accounts   
 - What is the typical use case   
 - How to create & edit these contracts   
 - How to send XEM from a multi-signature account.  
 
## What is a multi-signature contract 
NEM's multi-signature contracts work out of the box, ready to go with a push of a button and are universal, meaning they are built **into** the platform of the blockchain, not on top of the blockchain as in third-party reliant software for Bitcoin’s multisig. This unlocks various advantages and interesting possibilities for the user. But let’s first take a look at what a multi-signature contract is. The contract enables several people to administrate the activity of an account, control assets such as XEM from one account, other mosaics, or create additional contracts like when creating a new token. NEM’s multi-signature makes a contract that assigns rights and powers of a certain account to other accounts; this contract can be edited to suit most any needs. The contract converts a chosen regular account to a special multi-signature account. Now, this account cannot send funds on its own but is bound by the contract and administered accordingly to the contract via designated affiliated persons, i.e., cosigners. 
 
To illustrate this concept, take a look at Figure 1. Hannah has a NanoWallet account, and John has a NanoWallet account, but due to a multi-signature contract they also have accesses to a multi-signature account and can both use the funds in this account. The contract can be formed in a way such that **either** Hannah or John can separately use funds from the multi-signature account, i.e., "multi-user account", or that they **both** need to approve a transaction, i.e., "multisig account".
 
![Figure 1](http://i.imgur.com/UrE9Epm.png)
 
## What is the typical use case 
As you might already have discovered there can be a broad range of useful applications for multi-signature contracts and accounts. But let us take a look at some of the common use cases. The first use case is illustrated in Figure 2. Jonathan and Merryann live together, they have their own separate accounts, but they also need a shared account so that if Jonathan is out shopping, he can buy groceries for both him and Merryann. 
 
![Figure 2](http://i.imgur.com/yqr8xEv.png)
 
{'fraction_non_alphanumeric': 0.05392063793430796, 'fraction_numerical': 0.003037782418834251, 'mean_word_length': 4.070259865255053, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2146510', 'n_tokens_mistral': 1332, 'n_tokens_neox': 1274, 'n_words': 798}