 Show Posts
|
|
Pages: [1]
|
I'm seeing this too since late evening 3/29. Asks list is slightly incorrect, Bids list is severely distorted - whole price regions are missing. Tried FF14, MSIE9, Chrome24 - all show the same. "Group by price" doesn't help too. Clark, please have a look at it when you will have a chance! Thank you in advance!
Fixed. I've got a long-running process that polls the MtGox order book, and it works most of the time... Back to perfection! Thank you so much! |
|
|
|
Tonight I noticed that the market depth/order book is not updating correctly for some strange reason - if I freshly load the page, the order book will usually show old/incorrect order book data from an earlier point in time. Eventually it will merge into newer data, but it is still incorrect. If I leave the page open, orders are usually added & removed fairly often which tends to make it more correct, but it is usually out of date nevertheless. Is there perhaps cached order book data being stored somewhere that is causing this? I've noticed it happen on multiple computers this evening, especially when some large bids came in above $90, but when I refreshed the page they disappeared and it displayed incorrect cached? data. I also tried testing in a Chrome incognito window and it did the same thing too...
I'm seeing this too since late evening 3/29. Asks list is slightly incorrect, Bids list is severely distorted - whole price regions are missing. Tried FF14, MSIE9, Chrome24 - all show the same. "Group by price" doesn't help too. Clark, please have a look at it when you will have a chance! Thank you in advance! |
|
|
|
Have you imposed a hard limit of 100 outputs per transaction by any chance? Is there any way to relax it to, let us say, 200? I think there was a hard limit of 250 some time ago, but it was dropped afterwards, if I'm not mistaken?
Yes this is correct. The limit was reduced to 100 as some users where reporting problems with very large transactions not confirming and incurring unexpectedly high fees. I've adjusted the limit to 200 now, this should be enough for the vast majority of transactions. Were there any changes made to the logic of transactions with many small outputs? I'm having trouble with "Insufficient funds" error message again, now the balance of the first output from the drop-down list is quoted as available to send. It was Ok till late evening of 2/9/12 both in FireFox 13 and Chrome 24.0.1312.56. Thank you in advance for looking into this issue! |
|
|
|
Have you imposed a hard limit of 100 outputs per transaction by any chance? Is there any way to relax it to, let us say, 200? I think there was a hard limit of 250 some time ago, but it was dropped afterwards, if I'm not mistaken?
Yes this is correct. The limit was reduced to 100 as some users where reporting problems with very large transactions not confirming and incurring unexpectedly high fees. I've adjusted the limit to 200 now, this should be enough for the vast majority of transactions. Now it makes perfect sense, and sending coins works as expected. Thank you! |
|
|
|
I have altered the transaction output logic to prefer large value outputs over old outputs when the number of available outputs is very large. Please try again now.
Have you imposed a hard limit of 100 outputs per transaction by any chance? Is there any way to relax it to, let us say, 200? I think there was a hard limit of 250 some time ago, but it was dropped afterwards, if I'm not mistaken? |
|
|
|
Junko, may I ask you what browser/plugin combination you have used for these two transactions?
Google Chrome 24.0.1312.57 (Official Build 178923) m OS Windows WebKit 537.17 (@140072) JavaScript V8 3.14.5.6 Flash 11.5.31.138 User Agent Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17 Command Line "C:\Users\Roland\AppData\Local\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end Thank you! |
|
|
|
Thank you for your attention to this issue! The problem is still there, both in FireFox 13 (w/o Blokchain add-on) and Chrome 24.0.1312.56
Has your bitcoin address received a lot of very tiny transactions? This is likely the cause. I have altered the transaction output logic to prefer large value outputs over old outputs when the number of available outputs is very large. Please try again now. Right, this is the case. Now I'm also getting a warning "This wallet contains a very large number of unspent outputs. Please consolidate some outputs". May I ask how can I "consolidate some outputs"? |
|
|
|
Is this error resolved?
Tried 3rd, long-untouched wallet, both in FireFox 13 (w/o Blokchain add-on) and Chrome 24.0.1312.56 it gives error message "Insufficient Funds", while Received Funds correctly sum up to the Current Balance. I am also currently having problems sending from my blockchain.info wallet.
When I try to send, I get the message: "Insufficient funds. Value needed XXX BTC. Available amount xxx BTC"
I have well over the amount needed to send.
I see no errors in the Javascript console.
Is this error resolved? It may have been a temporary issue due to some of outputs being locked after failing to broadcast a transaction. This issue seems to be resolved - at least for me. I was able to successfully make two send transactions today with things appearing to be back to normal - again, for me at least. Junko, may I ask you what browser/plugin combination you have used for these two transactions? |
|
|
|
While creating custom single-recipient outgoing transaction, in both FireFox 13 and Chrome 24.0.1312.56, two of my wallets show "Insufficient funds"message and quote less than 30% of the actual listed wallet Final Balance as available for sending. Receive Money panel values add up to the Final Balance correctly. Have not encountered this problem up to 10:10am ET today. Should I be worried?  Thank you BlockChain devs for the great service! The problem is still there, both in FireFox 13 (w/o Blokchain add-on) and Chrome 24.0.1312.56 It may have been a temporary issue due to some of outputs being locked after failing to broadcast a transaction.
Doesn't look like usual temporary output lockup. |
|
|
|
While creating custom single-recipient outgoing transaction, in both FireFox 13 and Chrome 24.0.1312.56, two of my wallets show "Insufficient funds"message and quote less than 30% of the actual listed wallet Final Balance as available for sending. Receive Money panel values add up to the Final Balance correctly. Have not encountered this problem up to 10:10am ET today. Should I be worried? Thank you BlockChain devs for the great service! |
|
|
|
It is probably well known, but BlockChain sends outgoing transactions 100 times faster in Google Chrome v.24 compared to FireFox 13. Anyway, it was a nice surprise for me!  |
|
|
|
|
I would suggest "zero-trolling-tolerance" period as a newbie restriction instead - makes more sense to me.
|
|
|
|
|
Newbie restrictions idea seems pointless to me. Reporters of BlockChain newly introduced bugs ended up discussing them in the newbie section instead of the appropriate dedicated thread.
|
|
|
|
|
Unfortunally, I still have a problem with the BlockChain wallet that I've maid an outgoing transaction from on 2013-01-16 09:11:10. Transaction hasn't gone through, immediately after attempts to make outgoing transactions have been resulted in "... blocked to prevent double spends" error message. Afterwards till now attempts to make outgoing transaction in FireFox 13.0 bring the following error message:
"ConnectInputs: VerifySignature failed"
BlockChain devs, please have a look in it! Thank you in advance!
Update: I've just made a successful outgoing transaction from this wallet with Google Chrome Ver. 24.0.1312.52 m. Some inputs are still blocked from the previous unsuccessful outgoing transaction in FF 13.0, so I'll report the progress later.
|
|
|
|
when logging into blockchain.info wallet i get error : Error Decrypting Wallet. Please check your password is correct.
I get logged in, and i can see the amount of bitcoins available.
When creating new address I get : Error saving wallet. I'm facing the same problem since 1/18/2013 in FireFox 13.0. I could see incoming transactions appear, but unable to save Account Settings changes - red-background alert message "Error saving wallet" appears. Update: "Error Decrypting Wallet. Please check your password is correct" error message is gone now, 1/19/2003 5pm ET. Thank you, BlockChain devs! |
|
|
|
Hi, I was lurking around for more than a year, it is time now to come out of the shade! |
|
|
|
|
