<blockquote>
<p>When I, as the first signer, add my signature to the PSBT, where is this signed data stored while we wait for the second signer to add their signature?</p>
</blockquote>
<p>In the PSBT file.</p>
<blockquote>
<p>How does the PSBT format handle this interim state?</p>
</blockquote>
<p>The PSBT file format can be thought of as a set of key-value stores for each input and output of the transaction. When you add a signature to a PSBT, you add a field saying &quot;a signature for input X, with key Y, in Z&quot;. A future finalizer can then use this information (once enough other signatures have been added) to construct a valid transaction input.</p>
<blockquote>
<p>Are there any recommended security practices to ensure the integrity</p>
</blockquote>
<p>Not particularly. Generally, PSBT files are just an interchange format, for giving potential signers all the information they need to sign. This includes the (unsigned) transaction being signed, the UTXOs it is spending, information about scripts and keys that signers may need, and so forth. If the information is wrong/corrupted somehow, the outcome will just be an inability to sign, or the resulting signature will be invalid.</p>
<blockquote>
<p>and confidentiality of the partially signed transaction during this process?</p>
</blockquote>
<p>PSBTs do contain information that does not eventually end up on chain, and may be somewhat privacy-critical, such as the xpubs and key derivation paths used by the participants.</p>
<p>Because of this reason, it is not advisable to share the file with anyone but the other signers.</p>

CC BY-SA 4.0
2024-06-27T11:36:46.243Z
2024-06-27T11:54:47.100Z
2024-06-27T11:54:47.100Z
Pieter Wuille
<p>I'm currently working with Partially Signed Bitcoin Transactions (PSBTs) and trying to understand the best practices for handling transactions that require signatures from multiple parties. Specifically, I want to create a transaction that needs signatures from two different individuals using PSBT.</p>
<p>Storage of Signatures: When I, as the first signer, add my signature to the PSBT, where is this signed data stored while we wait for the second signer to add their signature? How does the PSBT format handle this interim state?</p>
<p>Security Concerns: Are there any recommended security practices to ensure the integrity and confidentiality of the partially signed transaction during this process?</p>
<p>I would appreciate any insights or guidance on managing multi-signature transactions using PSBTs, particularly regarding the secure storage and handling of the transaction until all required signatures are gathered.</p>

<transactions><blockchain><multi-signature><bip174-psbt><blockchain-data-storage>
Handling Multi-Signature Transactions with PSBT in Bitcoin
Nerses Asaturyan
# Handling Multi-Signature Transactions with PSBT in Bitcoin

(Asked by: username_0 on 2024-06-27)

I'm currently working with Partially Signed Bitcoin Transactions (PSBTs) and trying to understand the best practices for handling transactions that require signatures from multiple parties. Specifically, I want to create a transaction that needs signatures from two different individuals using PSBT.

Storage of Signatures: When I, as the first signer, add my signature to the PSBT, where is this signed data stored while we wait for the second signer to add their signature? How does the PSBT format handle this interim state?

Security Concerns: Are there any recommended security practices to ensure the integrity and confidentiality of the partially signed transaction during this process?

I would appreciate any insights or guidance on managing multi-signature transactions using PSBTs, particularly regarding the secure storage and handling of the transaction until all required signatures are gathered.

**Tags:** transactions, blockchain, multi-signature, bip174-psbt, blockchain-data-storage


---

## 1 answers

### Answer by username_1 on 2024-06-27. Score: 2 | Accepted answer

> When I, as the first signer, add my signature to the PSBT, where is this signed data stored while we wait for the second signer to add their signature?

In the PSBT file.

> How does the PSBT format handle this interim state?

The PSBT file format can be thought of as a set of key-value stores for each input and output of the transaction. When you add a signature to a PSBT, you add a field saying "a signature for input X, with key Y, in Z". A future finalizer can then use this information (once enough other signatures have been added) to construct a valid transaction input.

> Are there any recommended security practices to ensure the integrity

Not particularly. Generally, PSBT files are just an interchange format, for giving potential signers all the information they need to sign. This includes the (unsigned) transaction being signed, the UTXOs it is spending, information about scripts and keys that signers may need, and so forth. If the information is wrong/corrupted somehow, the outcome will just be an inability to sign, or the resulting signature will be invalid.

> and confidentiality of the partially signed transaction during this process?

PSBTs do contain information that does not eventually end up on chain, and may be somewhat privacy-critical, such as the xpubs and key derivation paths used by the participants.

Because of this reason, it is not advisable to share the file with anyone but the other signers.


---

