Help with transaction please

[btceic]

Hey guys,
I sent a transaction and bitcoin-qt client decided to set the fee to 0.00000001.

On blockchain.info it says it will take 24 hours to process:

http://blockchain.info/tx/20321adca2e952fcec518bb1226d8e7b87f41f54bc72d7394e0d8403fcce0312

Is there anyway to resend it with a larger fee or anyway to fix it?

TIA

[btceic]

Update: the transaction went through, took a few hours but it's all good now.

[CIYAM]

You can but it involves command line stuff to re-spend the coins with a higher fee, one will go through and the other will be denied as its a double spend. Tricky stuff, maybe someone's come up with an easy way but you'd be better off just waiting for it to go through, could take a couple of days but it will get there eventually.

I started a topic about this yesterday - unfortunately it is *not* possible to do what you are suggesting as once the network has *seen* the original UTXO being *spent* (regardless of being confirmed) it will *reject* any attempt to "double spend" (including forwarding such attempts).

You could only successfully achieve such an approach if (i) you can send the tx to a part of the network that has not yet seen the spend or (ii) the network has dropped the tx (which it might after a certain amount of time although that could be days).

[CIYAM]

Thanks, I wasn't too sure but that was the way I understood it from previous threads. Can you link that thread please? I'll try and get a bit better understanding of it.

No worries - the topic is here: https://bitcointalk.org/index.php?topic=327818.0 (I still have a stuck tx that I haven't been able to do anything about - and believe me I've tried all sorts of ways).

I think that the ease of making "double spend" attempts is greatly over-exaggerated.

[inform]

Maybe you need setings fix

[CIYAM]

Maybe you need setings fix

It has nothing to do with settings - it is the the way the Bitcoin network works. Nodes will simply not pass on "double spend" tx's.

The only way you can do that is to do them at the same time (which is not what this topic nor mine was talking about).

If it were really as simple as changing a setting you don't think that I or others with the same problem of stuck tx's wouldn't have already solved our problems?

[dserrano5]

(I still have a stuck tx that I haven't been able to do anything about - and believe me I've tried all sorts of ways).

Sad to hear that. Yesterday I broadcasted a no-fee tx to consolidate a couple of utxo's in my 12345 address into another one. It had priority 609.68M, way above 57.6M, yet it took nine hours to get its first confirmation.