<p>Yes, that is certainly possible. BIP 143 has examples of such transactions. Transactions that spend from both segwit outputs and non-segwit outputs are still vulnerable to transaction malleability.</p>

CC BY-SA 3.0
2017-07-20T16:24:21.923Z
2017-07-20T16:24:21.923Z
Ava Chow
<p>Yes, absolutely.</p>

<p>Every output can independently be a normal or SegWit output (when using P2SH-embedded SegWit, you can't even tell until it is being spent).</p>

<p>Every input can independently spend a normal output or SegWit output.</p>

<p>When a transaction has at least 1 SegWit <em>input</em> it's called a SegWit transaction.</p>

<p>When not all inputs are SegWit inputs, the transaction is still malleable.</p>

CC BY-SA 3.0
2017-07-20T16:58:40.687Z
Thanks Pieter. your answer and some readings here resolved most of my questions: https://bitcoincore.org/en/segwit_wallet_dev/
Shayan
CC BY-SA 3.0
2017-07-20T16:26:44.237Z
2017-07-20T16:26:44.237Z
Pieter Wuille
<p>I was wondering if it's feasible to compile a bitcoin transaction that is somewhere in between (segwit and non-segwit), maybe one of these scenarios. I'll call the non-segwit inputs, normal inputs just for the sake of simplicity.</p>

<ul>
<li>Use one normal UTXO input and one segwit input</li>
<li>Use Segwit inputs but have normal outputs</li>
<li>Have a transaction with two outputs, one Segwit and one normal</li>
</ul>

<p>If the answer to any of these is yes (maybe doesnt apply to the last scenario), what would be the case for transaction malleability? would the final transaction be still vulnerable to transaction malleability as the signature is still in the main transaction object? </p>

<transactions><segregated-witness><utxo><segwit2x>
Can there be a half segwit, half normal Bitcoin transaction?
Shayan
# Can there be a half segwit, half normal Bitcoin transaction?

(Asked by: username_0 on 2017-07-20)

I was wondering if it's feasible to compile a bitcoin transaction that is somewhere in between (segwit and non-segwit), maybe one of these scenarios. I'll call the non-segwit inputs, normal inputs just for the sake of simplicity.

* Use one normal UTXO input and one segwit input
* Use Segwit inputs but have normal outputs
* Have a transaction with two outputs, one Segwit and one normal

If the answer to any of these is yes (maybe doesnt apply to the last scenario), what would be the case for transaction malleability? would the final transaction be still vulnerable to transaction malleability as the signature is still in the main transaction object?

**Tags:** transactions, segregated-witness, utxo, segwit2x


---

## 2 answers

### Answer by username_2 on 2017-07-20. Score: 4 | Accepted answer

Yes, absolutely.

Every output can independently be a normal or SegWit output (when using P2SH-embedded SegWit, you can't even tell until it is being spent).

Every input can independently spend a normal output or SegWit output.

When a transaction has at least 1 SegWit *input* it's called a SegWit transaction.

When not all inputs are SegWit inputs, the transaction is still malleable.

> **Comments:**
> **username_0**: Thanks username_2. your answer and some readings here resolved most of my questions: https://bitcoincore.org/en/segwit_wallet_dev/  

---

### Answer by username_1 on 2017-07-20. Score: 3

Yes, that is certainly possible. BIP 143 has examples of such transactions. Transactions that spend from both segwit outputs and non-segwit outputs are still vulnerable to transaction malleability.


---

