WikileaksDude (OP)
|
|
October 31, 2013, 04:36:44 PM Last edit: November 01, 2013, 04:28:35 PM by WikileaksDude |
|
|
|
|
|
Rluner
|
|
October 31, 2013, 04:44:09 PM |
|
Don't panic, just give it time more, it happens sometimes.
|
|
|
|
WikileaksDude (OP)
|
|
October 31, 2013, 06:08:08 PM |
|
still not went through im getting scared lol
|
|
|
|
Rluner
|
|
October 31, 2013, 06:20:23 PM |
|
Just so you know I did check again, it's saying two minutes now, but the queue position is just under 300.
Good luck. I'm not sure why it's taking so long then now, sorry.
Update
That estimated timer is still all over the place.
Looking over the blockchain one of the inputs has loads of micro transactions, and the other has a few very regular 5 BTC transactions.
|
|
|
|
grue
Legendary
Offline
Activity: 2058
Merit: 1434
|
|
October 31, 2013, 06:53:13 PM |
|
here's an idea: stop using blockchain.info's wildly inaccurate "estimated confirmation time"
|
|
|
|
Cryddit
Legendary
Offline
Activity: 924
Merit: 1132
|
|
October 31, 2013, 07:03:04 PM |
|
This has two inputs -- one of which results from several hundred transactions (So, cashing it out is going to take some space in the blockchain) and the other of which has a confirmed but fairly recent transaction (so it may be delayed a little while things that the transaction processors are more sure of go first).
Did you include a tx processing fee, or is this thing queueing up for the very limited space in a block's free area?
|
|
|
|
WikileaksDude (OP)
|
|
October 31, 2013, 07:37:59 PM |
|
This has two inputs -- one of which results from several hundred transactions (So, cashing it out is going to take some space in the blockchain) and the other of which has a confirmed but fairly recent transaction (so it may be delayed a little while things that the transaction processors are more sure of go first).
Did you include a tx processing fee, or is this thing queueing up for the very limited space in a block's free area?
Hi, Cryddit. I transfered these from blockchain.info wallet.. they asked me to adjust the fees and I did it. as you can see i paid 0.0034 BTC in fees. Now its been hours... like this.
|
|
|
|
piuk
|
|
October 31, 2013, 08:48:08 PM Last edit: October 31, 2013, 09:07:10 PM by piuk |
|
Its very hard to accurately predict the confirmation time as:
a) The time between mined blocks varies b) The number of transactions in blocks varies c) It's impossible to predict if transactions will be made in future that bump yours down the queue. d) Unknown if the biggest miners have received your transaction of not.
So don't be surprised if the estimated confirmation time changes.
As far as I can tell, other than the transaction being very large, there is nothing which should prevent it confirming. I have rebroadcasted it manually now so hopefully that should help.
|
|
|
|
WikileaksDude (OP)
|
|
October 31, 2013, 09:02:10 PM |
|
Its very hard to accurately predict the confirmation time as:
a) The time between mined blocks varies b) The number of transactions in blocks varies c) It's impossible to predict if transactions will be made in future that bump yours down the queue. d) Unknown if the biggest miners have received your transaction of not.
So don't be surprised if the estimated confirmation time changes.
As far as I can tell other than the transaction being very large there is nothing which should prevent it confirming. I have rebroadcasted it manually now so hopefully that should help.
Thanks!
|
|
|
|
dserrano5
Legendary
Offline
Activity: 1974
Merit: 1029
|
|
October 31, 2013, 09:42:17 PM |
|
Its very hard to accurately predict the confirmation time as:
a) The time between mined blocks varies b) The number of transactions in blocks varies c) It's impossible to predict if transactions will be made in future that bump yours down the queue. d) Unknown if the biggest miners have received your transaction of not.
So don't be surprised if the estimated confirmation time changes. Agreed, that sounds hard. However the wild variations in the prediction turn this indicatior into something nearly useless. I've had transactions estimated to be confirmed within a few minutes, then 4 hours, then yay one confirmation! Wouldn't a more naive approach make more sense? E.g. taking into account only the position in the queue and some average block confirmation time, which would turn out to be around 7 minutes these days.
|
|
|
|
inform
Newbie
Offline
Activity: 42
Merit: 0
|
|
October 31, 2013, 10:33:34 PM |
|
maybe some fix
|
|
|
|
Rluner
|
|
October 31, 2013, 10:35:32 PM |
|
I have rebroadcasted it manually now so hopefully that should help.
Thanks! May I ask you please how you can rebroadcast it manually. Thanks in advance.
|
|
|
|
Ditto
|
|
October 31, 2013, 10:59:22 PM |
|
I have rebroadcasted it manually now so hopefully that should help.
Thanks! May I ask you please how you can rebroadcast it manually. Thanks in advance. https://blockchain.info/pushtx
|
|
|
|
Cryddit
Legendary
Offline
Activity: 924
Merit: 1132
|
|
November 01, 2013, 01:50:02 AM |
|
See, I think this is nuts. I mean, it's a pretty severe problem when a transaction can be out there for hours without getting into a block, especially with an appropriate tx fee paid.
Ten or twenty minutes is acceptable. Thirty ought to be something that's very rare.
But this is looking more and more like a service failure -- something about the P2P protocol that needs to be fixed.
We keep talking about "bitcoin is the future" - but the future has better service than this.
|
|
|
|
WikileaksDude (OP)
|
|
November 01, 2013, 03:28:23 PM Last edit: November 01, 2013, 04:55:16 PM by WikileaksDude |
|
See, I think this is nuts. I mean, it's a pretty severe problem when a transaction can be out there for hours without getting into a block, especially with an appropriate tx fee paid.
Ten or twenty minutes is acceptable. Thirty ought to be something that's very rare.
But this is looking more and more like a service failure -- something about the P2P protocol that needs to be fixed.
We keep talking about "bitcoin is the future" - but the future has better service than this.
almost a day (more than 12h) https://blockchain.info/tx/c07d47a5e1d023d0fd2c47c600a4ca178c7a2954754c88f3fb7f729bafb94539still unconfirmed.
|
|
|
|
Cryddit
Legendary
Offline
Activity: 924
Merit: 1132
|
|
November 01, 2013, 04:00:22 PM |
|
Okay, I'm not fully "up" on the ins & outs of mining.
But for what reasons do miners choose which transactions to include and exclude when they form a block?
Why wouldn't they take these transaction fees?
I'm here (invested in Bitcoin) because I believe that it's a Better Solution to transferring money via the Internet. And if it's failing to be a Better Solution I want to understand why, and what is necessary to fix it.
With more and more mentions in the news, Bitcoin is headed for a sort of "general awareness" as an option that it hasn't achieved now. But when it gets that sort of "general awareness" we don't want people experiencing service failures as their first interaction with it, because if that happens they'll drop it like a rock. This is one of the biggest reasons I'm concerned about mining and scalability; those are where we have the biggest vulnerabilities to failure.
If the miners are picking transactions to not process, or if the blockchain cannot handle it when one day we get slashdotted and it's hit with massive volume, then we have a fundamental problem that will prevent Bitcoin from achieving a critical mass of public acceptance and becoming what it could otherwise become -- a universal, easy, reliable, cheap way to transfer money via the Internet.
So, when something like this happens and the system isn't even terribly stressed, I am more than a little concerned. If we want public acceptance, we must have public trust. If we want public trust, then service failure is not an option.
|
|
|
|
WikileaksDude (OP)
|
|
November 01, 2013, 04:39:02 PM |
|
Hopefully the transaction will revert back. but I agree with you Cryddit. Also gavin and his team are working hard on this new fees system, hopefully he can fix bugs like these. Bitcoin is still BETA
|
|
|
|
drawingthesun
Legendary
Offline
Activity: 1176
Merit: 1015
|
|
November 01, 2013, 04:43:52 PM |
|
$5000 eternally trapped in limbo...
|
|
|
|
wizkid057
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
November 01, 2013, 05:11:41 PM |
|
As far as I can tell, other than the transaction being very large, there is nothing which should prevent it confirming. I have rebroadcasted it manually now so hopefully that should help.
2013-11-01 13:06:41 ERROR: CTxMemPool::accept() : not enough fees c07d47a5e1d023d0fd2c47c600a4ca178c7a2954754c88f3fb7f729bafb94539, 340000 < 350000 piuk: If you have the getrawtransaction style tx, I'll push it through on Eligius.
|
|
|
|
piuk
|
|
November 01, 2013, 05:37:10 PM |
|
2013-11-01 13:06:41 ERROR: CTxMemPool::accept() : not enough fees c07d47a5e1d023d0fd2c47c600a4ca178c7a2954754c88f3fb7f729bafb94539, 340000 < 350000
piuk: If you have the getrawtransaction style tx, I'll push it through on Eligius.
Frustrating it's only 0.0001 BTC out. If you are able to that would be great: http://pastebin.com/raw.php?i=uV10H0M6
|
|
|
|
|