diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 24, 2013, 10:10:29 AM |
|
hi i need some help i have sent some bitcoins and the transaction is unconfirmed although there is a fee. can someone please help me?
|
|
|
|
tysat
Legendary
Offline
Activity: 966
Merit: 1004
Keep it real
|
|
May 24, 2013, 10:55:18 AM |
|
Post a transaction ID or receiving/sending address.
|
|
|
|
diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 24, 2013, 11:21:50 AM |
|
this is the receiving address 199kbwU8TMtHqCaJ23cJrJbY7ArsSa97T3
|
|
|
|
tysat
Legendary
Offline
Activity: 966
Merit: 1004
Keep it real
|
|
May 24, 2013, 11:44:40 AM |
|
Guessing it's this transaction. Seems odd that it hasn't been confirmed yet as there's a 0.0005 fee attached. Maybe someone else will come along and have an idea.
|
|
|
|
diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 24, 2013, 11:47:29 AM |
|
yes its that transaction. how long do i have to wait untill it gets confirmed?
|
|
|
|
piuk
|
|
May 24, 2013, 11:48:36 AM |
|
The transaction is too large for a 0.0005 BTC fee. It is 17KB and the recommended fee is 0.0001 BTC per KB so a fee of about 0.0016 BTC would have been correct.
I think it will confirm but it could take 24 hours or more.
|
|
|
|
CIYAM
Legendary
Offline
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
|
|
May 24, 2013, 11:50:54 AM |
|
Agreed the fee should have been higher so it may take quite a while longer.
|
|
|
|
diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 24, 2013, 11:52:27 AM |
|
oh i didnt know that! what shall i do now? is there any way that it could get confirmed and i have no problem giving more as a fee
|
|
|
|
CIYAM
Legendary
Offline
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
|
|
May 24, 2013, 12:02:13 PM |
|
Unfortunately there is no way to add a fee to an existing tx (yet) so you will just have to be patient.
BTW how did you create the tx (as most standard clients should have calculated the correct fee for you)?
|
|
|
|
diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 24, 2013, 12:04:48 PM |
|
ok thank you very much!!! i hope the transaction gets confirmed...the fee came automatically 0.0005 from my android wallet
|
|
|
|
CIYAM
Legendary
Offline
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
|
|
May 24, 2013, 12:07:25 PM |
|
the fee came automatically 0.0005 from my android wallet
Aha - you might consider reporting this to the software vendor.
|
|
|
|
diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 24, 2013, 12:23:20 PM |
|
yes its that wallet. i informed them and they said they are going to work out the issue with the tx fees probably in the next release if theres any miner willing to confirm the transaction i ll send him a donation just to thank him. thank you guys informing me about the fee, even though it wasnt my fault i got a lesson
|
|
|
|
Andreas Schildbach
|
|
May 24, 2013, 01:01:41 PM |
|
I was just pointed to this thread. It's true Bitcoin Wallet does not correctly calculate the fee. It just has never been implemented, and also Bitcoin fee rules are currently changing quite a lot. As a workaround, Bitcoin Wallet currently just applies a default fee of 0.0005 BTC (the minimum for low-prio transactions). It happens that just days ago, Matt Corallo has published patches for bitcoinj to implement the correct fee rules to match with bitcoind/-qt 0.8.2. This will eventually make it into Bitcoin Wallet, as it is based on bitcoinj. However, before that happens, his patches need to be tested thoroughly and bitcoinj 0.9 needs to be released. At about that time, probably a new Bitcoin Wallet major release will happen. All in all, we have probably still some months to go. You can help speed things up by reviewing the code, write unit tests and help testing in general. In this case, feel welcome to subscribe to the bitcoinj mailing list at https://groups.google.com/forum/?fromgroups#!forum/bitcoinj As a user, you can work around this problem by refraining to receive lot of small value payments (e.g. dust). Its the small value incoming payments that make the outgoing payments huge in byte size (simplified). If you know you're building up a big transaction you can certainly pay a higher fee voluntary, but it's difficult given that the UI doesn't tell you how big (in bytes) your tx is going to be. Also see http://code.google.com/p/bitcoin-wallet/wiki/DustTransactions
|
|
|
|
diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 24, 2013, 01:15:05 PM |
|
yes they will be no more small transactions ( dust) for me anymore... thank you all i hope my transaction gets confirmed soon
|
|
|
|
diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 25, 2013, 09:14:11 AM |
|
is there any miner that can confirm my transaction please? my transaction is still unconfirmed
|
|
|
|
MorXpe
Newbie
Offline
Activity: 12
Merit: 0
|
|
May 25, 2013, 09:44:38 AM |
|
The transaction is too large for a 0.0005 BTC fee. It is 17KB and the recommended fee is 0.0001 BTC per KB so a fee of about 0.0016 BTC would have been correct.
I think it will confirm but it could take 24 hours or more.
Is there any way you can estimate transaction size (in KB)? Does Blockchain.info offer to set the transaction fee higher automatically when it would be advised?
|
|
|
|
Andreas Schildbach
|
|
May 25, 2013, 10:04:34 AM |
|
Does Blockchain.info offer to set the transaction fee higher automatically when it would be advised?
When I sent a transaction from blockchain.info just some days ago, it did not set a fee at all. I had similar problems to diseone, until days later the tx suddenly was confirmed.
|
|
|
|
kieras
Newbie
Offline
Activity: 43
Merit: 0
|
|
May 25, 2013, 11:04:55 AM |
|
what now?
|
|
|
|
diseone (OP)
Newbie
Offline
Activity: 14
Merit: 0
|
|
May 25, 2013, 12:40:25 PM |
|
what now?
still unconfirmed...
|
|
|
|
ranlo
Legendary
Offline
Activity: 1988
Merit: 1007
|
|
May 25, 2013, 01:04:25 PM |
|
The transaction is too large for a 0.0005 BTC fee. It is 17KB and the recommended fee is 0.0001 BTC per KB so a fee of about 0.0016 BTC would have been correct.
I think it will confirm but it could take 24 hours or more.
Just wanted to correct something here. You said 0.0001 BTC per KB is the "recommended fee." I made a transfer with that fee (it was a 7KB transaction so ended up being 0.0007 BTC) and it took a little over 3 days still. So I think it's recommended to add more than that.
|
|
|
|
|