<blockquote>
<p>I'm wondering how does one, using rpc or cli, perform a multi sig spend from physically separate machines?</p>
</blockquote>
<p>It is the usually the same exact process, just doing the signing command(s) on multiple devices. The software should be able to handle when it can't fully sign and will produce as many signatures as it can for that transaction.</p>
<blockquote>
<p>How does a signee know that there is a transaction that he/she needs to sign?</p>
</blockquote>
<p>He has to be given the transaction to sign. If using PSBT, the transaction will usually contain an identifier for the signer that the signer can look for to know whether to sign.</p>
<blockquote>
<p>Can a 2-of-3 transaction, that initially only contains 1 sig be broadcast then updated by 2nd or 3rd signatory?</p>
</blockquote>
<p>No, the transaction is not fully signed so it cannot be broadcast to the network. It must be given to one of the other signers and they must sign the transaction before it can be broadcast.</p>

CC BY-SA 4.0
2020-08-20T02:07:24.463Z
I read that question as "can a partially signed be broadcast to the network". Since it's not fully signed, it confuses me that you answered "Yes.". A partially signed transaction wouldn't relay, right? Could you please elaborate the last part of your answer? I feel like you must be talking about a different broadcast mechanism than what I was thinking.
Murch
CC BY-SA 4.0
2020-08-20T03:24:33.613Z
I just watched Andrews video discussing PSBT, and yes, youre right. The partially signed transaction cant be sent on the blockchain - and needs to be passed to the signers using something like email etc.
Magick
CC BY-SA 4.0
2020-08-20T04:53:27.700Z
@Murch Hmm, I think I misread that sentence.
Ava Chow
CC BY-SA 4.0
2020-08-20T00:03:05.520Z
2020-08-20T04:54:07.650Z
2020-08-20T04:54:07.650Z
Ava Chow
<p>I'm trying to learn more about doing multisig transactions.</p>
<p>The examples I've seen show the signing of the transaction with 2-of-3, or 3-of-3, where the signatures are added, essentially, at the same time, and same place.</p>
<p>I'm wondering how does one, using rpc or cli, perform a multisig spend from physically separate machines?</p>
<p>How does a signer know that there is a transaction that he/she needs to sign?</p>
<p>Can a 2-of-3 transaction, that initially only contains 1 signature be broadcast, then updated by the 2nd or 3rd signatory?</p>

<bitcoin-core><bitcoind><json-rpc><multi-signature><bitcoin-cli>
How is a multisig transaction transferred between multiple signers?
Magick
# How is a multisig transaction transferred between multiple signers?

(Asked by: username_0 on 2020-08-19)

I'm trying to learn more about doing multisig transactions.

The examples I've seen show the signing of the transaction with 2-of-3, or 3-of-3, where the signatures are added, essentially, at the same time, and same place.

I'm wondering how does one, using rpc or cli, perform a multisig spend from physically separate machines?

How does a signer know that there is a transaction that he/she needs to sign?

Can a 2-of-3 transaction, that initially only contains 1 signature be broadcast, then updated by the 2nd or 3rd signatory?

**Tags:** bitcoin-core, bitcoind, json-rpc, multi-signature, bitcoin-cli


---

## 1 answers

### Answer by username_1 on 2020-08-20. Score: 2 | Accepted answer

> I'm wondering how does one, using rpc or cli, perform a multi sig spend from physically separate machines?

It is the usually the same exact process, just doing the signing command(s) on multiple devices. The software should be able to handle when it can't fully sign and will produce as many signatures as it can for that transaction.

> How does a signee know that there is a transaction that he/she needs to sign?

He has to be given the transaction to sign. If using PSBT, the transaction will usually contain an identifier for the signer that the signer can look for to know whether to sign.

> Can a 2-of-3 transaction, that initially only contains 1 sig be broadcast then updated by 2nd or 3rd signatory?

No, the transaction is not fully signed so it cannot be broadcast to the network. It must be given to one of the other signers and they must sign the transaction before it can be broadcast.

> **Comments:**
> **username_2**: I read that question as "can a partially signed be broadcast to the network". Since it's not fully signed, it confuses me that you answered "Yes.". A partially signed transaction wouldn't relay, right? Could you please elaborate the last part of your answer? I feel like you must be talking about a different broadcast mechanism than what I was thinking.  
> **username_0**: I just watched Andrews video discussing PSBT, and yes, youre right. The partially signed transaction cant be sent on the blockchain - and needs to be passed to the signers using something like email etc.  
> **username_1**: @username_2 Hmm, I think I misread that sentence.  

---

