Quote from: il--ya on February 12, 2014, 12:19:13 AM

Quote from: nibyokwy on February 11, 2014, 11:35:53 PM

Quote from: itod on February 11, 2014, 10:25:02 PM

It really is not that much of a problem IMHO. If those change outputs will eventually confirm or not has nothing to do with mutated TxID. If someone wants to include unconfirmed change outputs as his new inputs that's his problem. .

it's not a matter of wanting to include unconfirmed change outputs, it's the fact that the satoshi client does this by default and you can't stop it without patching it. so user is vulnerable to getting their wallet messed up.

>it's not a matter of wanting to include unconfirmed change outputs, it's the fact that the satoshi client does this by default
is it a fact?

Yes. The QT client (and all other clients AFAIK) does NOT allow spending unconfirmed outputs received from outside the wallet. Change is treated differently and unconfirmed change is allowed to be spent. Under normal conditions this is actually a beneficial thing (otherwise you can end up not being able to spend coins until change outputs confirm) but right now that action is undesirable.