sendfrom fails while using zero-confirmation transaction #5383

issue alpdeniz opened this issue on November 26, 2014

alpdeniz commented at 11:17 PM on November 26, 2014: none

Bitcoind 0.9.3 cannot select zero-confirmation transaction output for sendfrom ["account" "addr" 0].

It should be free to use new transactions' inputs when explicitly defined.
laanwj added the label Wallet on Nov 27, 2014
laanwj added the label Bug on Nov 27, 2014
laanwj commented at 5:11 PM on February 16, 2016: member

Bitcoin Core's wallet regards outputs of its own outgoing zero-conf transactions as spendable (unless -spendzeroconfchange=0), but not those of incoming transactions.

Spending the outputs of other people's transactions before they are confirmed is, in general, unsafe. Various malleability issues make that unreliable.
laanwj closed this on Feb 16, 2016
promag commented at 7:59 PM on February 16, 2016: member

@laanwj And fundrawtransaction should be able to select those zero-conf UTXOs? Even if they are watch only?
laanwj commented at 8:47 AM on February 17, 2016: member

@promag Wouldn't be against making it configurable, but by default it should have the same behavior as the other send* options I'd say.
DrahtBot locked this on Sep 8, 2021

Contributors

Labels