Sorry, talking crap - had it in my head that the new dust checks were already included in 0.8.1, so most nodes would reject the tx.
nope, it's in 0.8.2. 
Topic: [CONFIRMED] Why not confirming? Over 0.01 under 10k size, even includes a fee... - page 2. (Read 1922 times)
May 17, 2013, 10:10:19 PM
May 17, 2013, 08:13:16 PM
as long as it will eventually confirm I dont mind waiting, Just so long as it doesnt NEVER confirm.
I'll put the fee back up to 0.0005 - all my tx have gone thru fine with that. Using official client I can get insane tx fees like 0.05 BTC. But thats my whole purpose for doing this. To consolidate my coins by sending from one wallet to another and then back.
I'll put the fee back up to 0.0005 - all my tx have gone thru fine with that. Using official client I can get insane tx fees like 0.05 BTC. But thats my whole purpose for doing this. To consolidate my coins by sending from one wallet to another and then back.
May 17, 2013, 08:08:22 PM
It will eventually get relayed once it hits a node that doesn't mind doing "spammish" transactions, but you could be waiting a good couple of hours.
There are a few of these nodes out there, and you can set up your client to always connect to them if you do a lot of transactions like this.
Have a look at that link again, with advanced options on:
http://blockchain.info/tx/9375925ed95d85cd9b5ecda6332c814c35ebf04124ac625da4c0bf10ab597767?show_adv=true
You have quite a few low outputs assigned to one address, so you (I believe) would have needed to include a greater fee: 0.0001BTC as a fee is pretty low/borderline for any transaction (IMO).
There are a few of these nodes out there, and you can set up your client to always connect to them if you do a lot of transactions like this.
Have a look at that link again, with advanced options on:
http://blockchain.info/tx/9375925ed95d85cd9b5ecda6332c814c35ebf04124ac625da4c0bf10ab597767?show_adv=true
You have quite a few low outputs assigned to one address, so you (I believe) would have needed to include a greater fee: 0.0001BTC as a fee is pretty low/borderline for any transaction (IMO).
May 17, 2013, 08:08:16 PM
Well thats a HUGE issue, if the change generated by your tx is going to get flagged as dust and thus your tx will never confirm.
How could no one have thought of or picked up on that!?
How could no one have thought of or picked up on that!?
This will only be a problem if the mining pools all switch to 0.8.2 and you use a client version (< 0.8.2) which generates dust change outputs.
May 17, 2013, 07:59:33 PM
Well thats a HUGE issue, if the change generated by your tx is going to get flagged as dust and thus your tx will never confirm.
How could no one have thought of or picked up on that!?
How could no one have thought of or picked up on that!?
May 17, 2013, 07:52:49 PM
Sorry, talking crap - had it in my head that the new dust checks were already included in 0.8.1, so most nodes would reject the tx.
May 17, 2013, 07:50:00 PM
Also I've sent almost half a million dust transactions ... they've all confirmed fine ?
May 17, 2013, 07:47:33 PM
The second output .. is the change. I didnt put that there.
May 17, 2013, 07:44:48 PM
Your second output is considered 'dust', so your transaction won't get relayed.
May 17, 2013, 07:31:21 PM
http://blockchain.info/tx/9375925ed95d85cd9b5ecda6332c814c35ebf04124ac625da4c0bf10ab597767
Total Input 0.0569188 BTC
Total Output 0.0568188 BTC
Fees 0.0001 BTC
Estimated BTC Transacted 0.0568 BTC
Size 1662 (bytes)
Received Time 2013-05-17 03:46:52
Estimated Confirmation Time Very Soon ?
I was under the impression that after 05/15 that the min tx fee was going down to 0.0001 - even still this tx should qualify for NO TX FEE ... So why hasnt it confirmed in almost a whole day ?
Total Input 0.0569188 BTC
Total Output 0.0568188 BTC
Fees 0.0001 BTC
Estimated BTC Transacted 0.0568 BTC
Size 1662 (bytes)
Received Time 2013-05-17 03:46:52
Estimated Confirmation Time Very Soon ?
I was under the impression that after 05/15 that the min tx fee was going down to 0.0001 - even still this tx should qualify for NO TX FEE ... So why hasnt it confirmed in almost a whole day ?
Jump to: