I've got a bit of a problem with the Bitcoin Daemon starting to use multiple unconfirmed input to chain new transactions. For example, I've had to manually submit a transaction (https://blockchain.info/tx/35c4e8c86075cf3f5335e029abd2d981af011c142b56e04c0a6d8b0d588d32ae) to the blockchain.info database because it's input is currently unconfirmed. As a result, this transaction cannot confirm until all its ancestors have confirmed. This behavior has only recently started becoming noticeable (not sure if it was prevalent before or is something to do with potential fragmentation in the wallet?) and I'm wondering is it a symptom of the significant increase in user traffic resulting in miners becoming more 'picky' and as a result, chained transactions appearing because an ancestor that maybe is valid but didn't include a fee, are being ignored for long periods?
Second question, is there any way I can mitigate this behavior so that only confirmed outputs are used as inputs?
* Edit: Provided better example link
Topic: Stopping Bitcoin Daemon using unconfirmed inputs (Read 741 times)
Jump to: