<p>If I know the m of n values of the multisig, the # of inputs (all of which are from the multisig and require m signatures) and outputs and the redeem script, how can I determine the size of the transaction after m signatures?</p>

CC BY-SA 4.0
2018-12-22T00:39:32.427Z
@JBaczuk there doesn't seem to be an accepted answer there, nor does the existing answers fully provide an answer.
tipu
CC BY-SA 4.0
2018-12-22T09:05:32.407Z
@tipu to me it seems that the voted answer in the other question fits and answers your question.  It assumes that `p2sh-multisig` is being redeemed, all pubkeys are compressed (33 bytes per pubkey) and that the signatures produced are 72 bytes each.  If you're asking about segwit specifically (the calculation will be a bit different in that case), then please edit your question.  Otherwise I agree that it's a duplicate.
arubi
<raw-transaction><multi-signature>
Determining the byte size of multisig transaction beforehand knowing the details of the transaction
tipu
# Determining the byte size of multisig transaction beforehand knowing the details of the transaction

(Asked by: username_0 on 2018-12-21)

If I know the m of n values of the multisig, the # of inputs (all of which are from the multisig and require m signatures) and outputs and the redeem script, how can I determine the size of the transaction after m signatures?

**Tags:** raw-transaction, multi-signature

> **Comments:**
> **username_0**: @JBaczuk there doesn't seem to be an accepted answer there, nor does the existing answers fully provide an answer.  
> **username_1**: @username_0 to me it seems that the voted answer in the other question fits and answers your question.  It assumes that `p2sh-multisig` is being redeemed, all pubkeys are compressed (33 bytes per pubkey) and that the signatures produced are 72 bytes each.  If you're asking about segwit specifically (the calculation will be a bit different in that case), then please edit your question.  Otherwise I agree that it's a duplicate.  

---

## 0 answers

