Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: paulkoan on November 09, 2013, 09:14:27 PM



Title: Low fee on transaction to mtgox - send again?
Post by: paulkoan on November 09, 2013, 09:14:27 PM


I have sent a transaction to mtgox, blockinfo reports that the network fee is lower than recommended, so it will take quite a long while to get confirmed.

I was thinking I can send another transaction with more attractive fees - but that represents two difficulties:

  •     I don't know why the client didn't calculate the correct fee
  •     mtgox uses a single address per transaction, and so I won't get a new one until the current one completes. If I send another transaction to the current address, when the slow one finally gets there, it will go to the wrong address.
I am not sure what is the best way forward. I am using bitcoind v80500.

Is there a way I can get a transaction into mtgox without breaking the one I have currently waiting for confirmation, and if so, how can I get the fees to be right?


Title: Re: Low fee on transaction to mtgox - send again?
Post by: FreakNet on November 09, 2013, 09:23:27 PM
Patience is a virtue, my dear friend. Just wait it out.


Title: Re: Low fee on transaction to mtgox - send again?
Post by: cfrm on November 09, 2013, 09:24:43 PM
I sent three transactions two days ago with no fee. Took  36 hours for the slowest one to get through. The two others were approx half that time.

So yea, patience.


Title: Re: Low fee on transaction to mtgox - send again?
Post by: paulkoan on November 10, 2013, 04:41:37 AM
Thanks for the replies, however they don't seem to be in response to my question.


Title: Re: Low fee on transaction to mtgox - send again?
Post by: paulkoan on November 19, 2013, 12:50:16 AM

The transaction in question was submitted to the network on 1384203200, or Mon, 11 Nov 2013 20:53:20 GMT - so 8 days ago.

Multiple rescans later, and still at zero confirmations.

I did another test today for another transaction, and this also looks like it won't go through, with blockchain.info reporting that the fees are too low.  Again, this is a transaction with multiple inputs, and so the same result may happen:

https://blockchain.info/tx/3576f61b9f12069c9c6def65b0eac0e5b1ef6f974600e5ab46807d18a4e15c08

I still don't understand why the client - given that it knows the amount of inputs involved, and the resultant size of the transaction, would not scale the fee accordingly.  Is this a configuration issue perhaps?