<blockquote>
<p>A single output is roughly 34 bytes per output regardless of whether the output represents a standard address or multisig address. Is this correct?</p>
</blockquote>
<p>Yes, in modern Bitcoin transactions the size of producing an output (ie, paying to an address) is constant and has no relation to the size of the actual script. For native segwit outputs the size is somewhat larger (42 bytes) due to a safer hash function being used, but this is still unrelated to the size of the script.</p>
<blockquote>
<p>In other words, the higher price for a MultiSig only matters when it's being used as the input of a transaction, not the output?</p>
</blockquote>
<p>Yes, the cost of using a larger multisig transaction is born by the person who owns the keys, which makes sense economically. In the original transaction type of Bitcoin (P2PK) this was not the case, and the additional cost was born by the person sending money, which didn't make a great deal of sense economically.</p>

CC BY-SA 4.0
2021-01-29T01:03:01.043Z
2021-01-29T01:03:01.043Z
Claris
<p>Based on my research the cost to transfer funds <em>from</em> a 2/3 MultiSig address to any other address (be it a standard or MultiSig address) is approx. 2 x the cost of transferring funds from a standard address to another address since it <a href="https://bitcoin.stackexchange.com/a/55153/78451">consumes approx. 2 x the amount of data</a> (147 bytes vs. 295 bytes) (pretty costly!).</p>
<p>A single output is roughly 34 bytes per output regardless of whether the output represents a standard address or multisig address. Is this correct? In other words, the higher price for a MultiSig only matters when it's being used as the input of a transaction, not the output?</p>
<p>If so, does the data size grow linearly with each additional signature? (i.e, what would be the approx. number of bytes for a 2/2 and a 3/4 MultiSig transaction)?</p>
<p>Thanks</p>

<transactions><address><transaction-fees><multi-signature>
Fees for Multisig Addreses Twice as High as Standard Address?
S.O.S
# Fees for Multisig Addreses Twice as High as Standard Address?

(Asked by: username_0 on 2021-01-29)

Based on my research the cost to transfer funds *from* a 2/3 MultiSig address to any other address (be it a standard or MultiSig address) is approx. 2 x the cost of transferring funds from a standard address to another address since it [consumes approx. 2 x the amount of data](https://bitcoin.stackexchange.com/a/55153/78451) (147 bytes vs. 295 bytes) (pretty costly!).

A single output is roughly 34 bytes per output regardless of whether the output represents a standard address or multisig address. Is this correct? In other words, the higher price for a MultiSig only matters when it's being used as the input of a transaction, not the output?

If so, does the data size grow linearly with each additional signature? (i.e, what would be the approx. number of bytes for a 2/2 and a 3/4 MultiSig transaction)?

Thanks

**Tags:** transactions, address, transaction-fees, multi-signature


---

## 1 answers

### Answer by username_1 on 2021-01-29. Score: 3

> A single output is roughly 34 bytes per output regardless of whether the output represents a standard address or multisig address. Is this correct?

Yes, in modern Bitcoin transactions the size of producing an output (ie, paying to an address) is constant and has no relation to the size of the actual script. For native segwit outputs the size is somewhat larger (42 bytes) due to a safer hash function being used, but this is still unrelated to the size of the script.

> In other words, the higher price for a MultiSig only matters when it's being used as the input of a transaction, not the output?

Yes, the cost of using a larger multisig transaction is born by the person who owns the keys, which makes sense economically. In the original transaction type of Bitcoin (P2PK) this was not the case, and the additional cost was born by the person sending money, which didn't make a great deal of sense economically.


---

