Quote from: webbrowser on October 04, 2014, 01:01:44 PM

Quote from: ABitInterested on October 04, 2014, 03:29:14 AM

Update

A few things.

First of all the unconfirmed transaction is still unconfirmed. If anyone knows what I did wrong please enlighten me. The date I sent this isn't even correct so it looks like it was rebroadcast or something? The fee paid was .00011 which is what I always use on these transactions but it does say "low priority".

https://blockchain.info/tx/cbfb10bdcb2a1f92970dc5e9f6b0ea8069870eed4a1564299bab33b5daaa19aa

I'm no expert on these matters, but I think it goes like this. The transation's priority is affected by the age of the inputs, size of the transaction (in btc and in bytes), and transaction fee. This is to reward the miner and protect the network from lots of tiny dust transactions. Unfortunately, the priority is low because because you usually send payments out right after coinbase sends it to you, large packet size with multiple small btc outputs, and apparently a small transaction fee. And so if there aren't any miners who are willing to include this transaction in their newly mined blocks, the transaction isn't confirmed.

If the transaction isn't confirmed for some period of time, blockchain.info assumes that it won't be confirmed and forgets it and "returns" the coins to your wallet. But all the signatures in the original transaction are still valid, so if some other miner retains the transaction in its memory and rebroadcasts it, it re-enters blockchain's memory with a different date.

At this point, that transaction might still eventually get confirmed, but it might not. Not sure if you can just ignore it. Or just re-spend the coins that were returned to your wallet. Or, in some wallets, I think you can add extra transaction fees to the transaction to increase its priority.

Not sure how to avoid this in future. Keep some coins in your wallet and pay out from that? Pay less frequently so that the btc amount is larger? Pay the recommended transaction fee?

I think thats correct but to be sure i suggest contacting blockchain.info because they might have some special settings. So its most probably best to ask them instead assuming it will work like normal bitcoin clients would handle it.