<p>It is basically never a good idea to be spending from an unconfirmed transaction, regardless of transaction malleability fixes or other improvements. Unconfirmed transactions are not final and thus you shouldn't be spending from them unless you are willing to take the risk that transactions in the unconfirmed transactions chain can become invalidated. Since a transaction malleability fix is not a consensus rule yet, transactions are still malleable (and can still be after segwit too) and can be vulnerable to transaction malleability attacks.</p>

<p>As with any other transaction, you should only spend from it after it has at least 1 confirmation.</p>

CC BY-SA 3.0
2017-06-16T07:08:41.857Z
2017-06-16T07:08:41.857Z
Ava Chow
<p>Reading about spending own generated unconfirmed change some time ago I stumbled upon <a href="http://www.reddit.com/r/Bitcoin/comments/1xm49o/due_to_active_malleable_transaction_relayers_it/" rel="noreferrer">this reddit thread</a>  that convinced me that doing so is a really bad idea and could prove catastrophic for any business that allows it.</p>

<p>Now in the <a href="https://bitcoin.org/bin/0.9.0/README.txt" rel="noreferrer">bitcoin core 0.9.0 release notes</a> there are some fixes regarding the infamous malleability issue (search for text: "Transaction malleability-related fixes").</p>

<p>My question is pretty straightforward: </p>

<ul>
<li>Is it now safe to spend unconfirmed change generated by my own txs, after the 0.9.0 upgrades?</li>
<li>If not, what is considered to be a safe number of confirmations for this change before I can use it as an input for another tx?</li>
</ul>

<confirmations><change><transaction-malleability><unconfirmed-transactions>
Spending own generated unconfirmed change in the v.0.9.0 era
Doug Peters
# Spending own generated unconfirmed change in the v.0.9.0 era

(Asked by: username_0 on 2014-03-24)

Reading about spending own generated unconfirmed change some time ago I stumbled upon [this reddit thread](http://www.reddit.com/r/Bitcoin/comments/1xm49o/due_to_active_malleable_transaction_relayers_it/) that convinced me that doing so is a really bad idea and could prove catastrophic for any business that allows it.

Now in the [bitcoin core 0.9.0 release notes](https://bitcoin.org/bin/0.9.0/README.txt) there are some fixes regarding the infamous malleability issue (search for text: "Transaction malleability-related fixes").

My question is pretty straightforward:

* Is it now safe to spend unconfirmed change generated by my own txs, after the 0.9.0 upgrades?
* If not, what is considered to be a safe number of confirmations for this change before I can use it as an input for another tx?

**Tags:** confirmations, change, transaction-malleability, unconfirmed-transactions


---

## 1 answers

### Answer by username_1 on 2017-06-16. Score: 2

It is basically never a good idea to be spending from an unconfirmed transaction, regardless of transaction malleability fixes or other improvements. Unconfirmed transactions are not final and thus you shouldn't be spending from them unless you are willing to take the risk that transactions in the unconfirmed transactions chain can become invalidated. Since a transaction malleability fix is not a consensus rule yet, transactions are still malleable (and can still be after segwit too) and can be vulnerable to transaction malleability attacks.

As with any other transaction, you should only spend from it after it has at least 1 confirmation.


---

