<p>Yes, you are right. There are two ways of doing so:</p>

<p>You can create a multi-sig transaction as you mentioned, including a m-of-n script in which you will define the number of signatures (m) of the total n that will be necessary  to redeem from the transition. The script structure from T2 will be:</p>

<pre><code>ScriptPubKey: &lt;m&gt; &lt;PubKey_1&gt; &lt;PubKey_2&gt; ... &lt;PubKey_n&gt; n
</code></pre>

<p>And the redeem script from T3 will be:</p>

<pre><code>ScriptSig: &lt;Sig_1&gt;&lt;Sig_2&gt; ... &lt;Sig_n&gt;
</code></pre>

<p>Notice that, in order to be valid, the signatures in T3 must be in the same order as the public keys in T2. </p>

<p>On the other hand, you can encapsulate the multi-sig scripts mentioned avobe in a Pay-to-scriptHash, in that way the first transaction script (T2) will simpler, since it will be just a hash, and the transaction will look more similar to a traditional Pay-to-Publickey-hash. </p>

CC BY-SA 3.0
2017-04-11T13:44:36.497Z
2017-04-11T13:44:36.497Z
sr_gi
<p>Assume, I received a bitcoin in a regular transaction: T1. But I need to make MULTISIG transaction. so there should be at least n out of m signatures in new transaction :T3, to redeem it. </p>

<p>Am I right that to turn T1 to a MULTI-SIG one I need to do as follows:</p>

<p>1- I create new transaction T2, that points to T1, and includes all the m public keys and it pays to myself.</p>

<p>2- When I want to pay someone, I create new transaction: T3 (pointing to T2) includes n signatures and pays to another party.</p>

CC BY-SA 3.0
2017-04-11T12:12:35.577Z
There is no such thing as "multisig transaction". There is "multisig address". Transaction just a way to transfer bitcoin from one address(es) to another one(s)
amaclin
<multi-signature>
How to convert regular transaction to MULTI-SIG one?
user153465
# How to convert regular transaction to MULTI-SIG one?

(Asked by: username_0 on 2017-04-11)

Assume, I received a bitcoin in a regular transaction: T1. But I need to make MULTISIG transaction. so there should be at least n out of m signatures in new transaction :T3, to redeem it.

Am I right that to turn T1 to a MULTI-SIG one I need to do as follows:

1- I create new transaction T2, that points to T1, and includes all the m public keys and it pays to myself.

2- When I want to pay someone, I create new transaction: T3 (pointing to T2) includes n signatures and pays to another party.

**Tags:** multi-signature

> **Comments:**
> **username_1**: There is no such thing as "multisig transaction". There is "multisig address". Transaction just a way to transfer bitcoin from one address(es) to another one(s)  

---

## 1 answers

### Answer by username_2 on 2017-04-11. Score: 1

Yes, you are right. There are two ways of doing so:

You can create a multi-sig transaction as you mentioned, including a m-of-n script in which you will define the number of signatures (m) of the total n that will be necessary to redeem from the transition. The script structure from T2 will be:

```
ScriptPubKey: <m> <PubKey_1> <PubKey_2> ... <PubKey_n> n

```

And the redeem script from T3 will be:

```
ScriptSig: <Sig_1><Sig_2> ... <Sig_n>

```

Notice that, in order to be valid, the signatures in T3 must be in the same order as the public keys in T2.

On the other hand, you can encapsulate the multi-sig scripts mentioned avobe in a Pay-to-scriptHash, in that way the first transaction script (T2) will simpler, since it will be just a hash, and the transaction will look more similar to a traditional Pay-to-Publickey-hash.


---

