user1546: I have sent a (>10000 byte) 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?

user7636: There is no correct fee for sending BTC to mtgox, and you can send to the same address. MtGox doesn't get the fee. MtGox only requires a number of confirmations. If you added a fee at all then there should be no extraordinary delay. A fee-related delay is for the first confirmation. The age of your source account(s) can make more difference than a fee. Just relax. The first time is painful to wait for. 


I've updated...


I don't know how you can send a ">10000 byte" transaction to mtgox unless you are talking about the bytes of a raw transaction rather than a bitcoin amount. In that case, you should be able to figure this out. Send the same amount again from same addresses but with a higher fee. It is a double-spend and the network may take the second first while leaving the first to be discovered invalid.

1546: <p>I have sent a (>10000 byte) transaction to mtgox, blockinfo reports that the network fee is lower than recommended, so it will take quite a long while to get confirmed.</p>

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

<ol>
<li>I don't know why the client didn't calculate the correct fee</li>
<li>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.</li>
</ol>

<p>I am not sure what is the best way forward.  I am using bitcoind v80500.</p>

<p>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?</p>
 7636: <p>There is no correct fee for sending BTC to mtgox, and you can send to the same address. MtGox doesn't get the fee. MtGox only requires a number of confirmations. If you added a fee at all then there should be no extraordinary delay. A fee-related delay is for the first confirmation. The age of your source account(s) can make more difference than a fee. Just relax. The first time is painful to wait for. </p>

<blockquote>
  <blockquote>
    <p>I've updated...</p>
  </blockquote>
</blockquote>

<p>I don't know how you can send a ">10000 byte" transaction to mtgox unless you are talking about the bytes of a raw transaction rather than a bitcoin amount. In that case, you should be able to figure this out. Send the same amount again from same addresses but with a higher fee. It is a double-spend and the network may take the second first while leaving the first to be discovered invalid.</p>
