Am I the only one who had problems with the API withdrawal?
Only getting "Unknown Error"
With JSON RPC? Using which method and parameters? |
|
|
|
Looking at the address provided in the previous thread - http://blockchain.info/address/1mCs4bfGXxyU7UbZgx1N2eEGpErFMNTwk it seems that all of the transactions have confirmed now. The problem stems from the fact you have received many hundreds of small transactions. This causes subsequent transactions that spend them to incur high fees and often confirm slowly. |
|
|
|
settxfee is now enabled in the JSON RPC api. |
|
|
|
There would still be a risk of it not get confirmed since the fee is not what it should be (> 0.0005).
Can't you make it send the correct fee? (like it should)
You can now use the settxfee JSON RPC command to set the default transaction fee for 24 hours http://blockchain.info/api/json_rpc_apior set fee policy to generous in the javascript interface to increase the base fee to 0.001 BTC |
|
|
|
And I did the same thing today, I'm getting sick of blockchain.info support, they take forever to reply.
It's not my fault if I've set the goddamn fee to generous but it still goes out with 0.0005 BTC fee.
I'm temporarily suspending payments, this is causing too much mess.
Why not limit the number of outputs in each transaction? |
|
|
|
|
Did you import the private key into Mt.Gox? If so they are probably sweeping the funds.
|
|
|
|
Hi piuk, I noticed that the receive api callback from blockchain.info is no longer immediate. I was accepting zero-confirmation payments successfully up until maybe a couple of weeks ago. Here is an example of a generated address for which I'm still awaiting blockchain.info's response: https://blockchain.info/address/14TdZ3nRTcfLUkRUb8DUTXUZf8Pe6pPwEGDid you make a change to the callback so it no longer responds immediately? No, no changes have been made to the callbacks recently. Is it the both the forwarding payment and callback the callback which is being delayed or just the callback? Could you add the ability to archive/unarchive multiple address at once?
Like a check box next to each address and a button to Archive/Unarchive those addresses.
The unarchived icons are pretty quick to tap for me. I can see a need to a checkbox for archive but the interface needs to be kept uncluttered at the same time. I've set the 'Default Fee Policy' to 'Generous', but my transactions are still being send with 0.0005 BTC fee. What's going on? (I'm using 'Bitcoin-Qt Compatible JSON RPC', 'sendmany') The fee policy set in the javascript interface does not currently affect the API. However I have fixed this my development version and it will be fixed next update. Is anyone else getting "Unrecognized search pattern" on every bitcoin address lookup?
This should be fixed now. Also fixed a bug related to the "address contains a very large number of unspent outputs" issues. |
|
|
|
Send the 0.069 BTC to yourself (generate a new address) to consolidate some inputs, you may be able to spend the full amount after that or if not send another transaction to yourself until you are able to.
Ive just been able to send 0.068 BTC (rounded) to my Mt Gox Wallet. The second transfer comes up with: "Insufficent funds. Vaklue needed 1.00 BTC Availiable amount 0.06916666" Do I keep sending 0.068 BTC (rounded) until I can send the full amount? Yes, keep sending in smaller amounts. You must have a serious amount of 0.0001 BTC inputs to make up 10 BTC. Would you you mind posting your bitcoin address? |
|
|
|
Ok, so blockchain.info just dropped all these transactions from their memory pool. That's better. So we are still waiting for the initial transaction to make it into a block.
If another nodes relays us the transaction again it will reappear on the site but for now it has been removed from the memory pool as it seems unlikely it will confirm. |
|
|
|
|
Send the 0.069 BTC to yourself (generate a new address) to consolidate some inputs, you may be able to spend the full amount after that or if not send another transaction to yourself until you are able to.
|
|
|
|
|
Because we are one of the few services with a sufficiently large transaction volume, large hot wallet and the ability to calculate taint. We also take the risk of accepting zero conf transactions.
I am not adverse to lowering the fees. Those of you who feel a 1.5% fee is too high would you use the service at a 0.5% fee?
|
|
|
|
Hi, I noticed that I no longer get a profit/loss result for satoshidice on blockchain.info - is there a limit to the number of bets or addresses for this functionality to be enabled - I found it quite useful  Will I've enabled the profit/loss again now. It was disabled due to high load but things are a little more stable now. Hey piuk, I assume the above didn't make it into your busy schedule for the past weekend but would you perhaps have a new ETA for it? Just curious..
Sorry Hazek, I did not get time to work on the charts this weekend. Unfortunately due to the downtime some other things had to take priority, like setting up a proper monitoring and alert system since pingdom isn't cutting it anymore. I don't have an ETA at the moment. |
|
|
|
Yeah that's kinda strange, can anybody tell me whether I should upgrade or not?
Yes please do. The old blockchain app has a security vulnerability where it is possible to transfer money without any kind of password when double encryption isn't activated. I hope this is solved now.
What is actually happening is you have entered the second password once and it is being remembered a second time. I am aware of this issue and it will be fixed next update. |
|
|
|
Is this something you would consider? Blockchain info for testnet and the API to test on? It would be a little nicer from a development standpoint to test applications with play money before real BTC start flying around in beta code.
Possibly, It would need to be run on a separate database/server but I could certainly see it being useful. 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!
I haven't made any changes since then. May I ask the bitcoin address again? ------------- UK Deposit fees reduced 2.97% - 4.7% (Further fee reductions will be coming next week). Sofort now available for Austria, Belgium, Germany, Netherlands, Poland, Switzerland, United Kingdom More info: http://blockchain.info/wallet/deposit-methods |
|
|
|
4) At this point there was a brief pop up, something about saving the wallet (not sure of exact text) Was it per chance this popup:  Please PM your identifier and I can send you a zip containing all backups of the wallet but if the key did not sync then unfortunately they won't help. |
|
|
|
Done, added coinbase tag on all our poolservers: "Hi from 50BTC.com 1", "Hi from 50BTC.com 2"...."Hi from 50BTC.com 7"
Thank you, added. Do you provide API support for test net?
No not currently. This is missing in the Chrome app.
It will be getting an update in a day or two with some other changes. As the javascript cannot be changed remotely it can lag behind a bit. ------- The migration of the final Innodb tables to Cassandra is now complete. A MySQL crash will no longer be enough to bring the site down and I am confident there will be no more downtime anytime soon. The Site is now running 4 Ndb nodes, 3 Bitcoind instances, 2 Cassandra nodes, 2 MySQL nodes and 2 Tomcat instances. |
|
|
|
|
The data come directly from Mt.Gox so I'm not sure if it is a problem on our side or their. I will keep an eye of for it occurring again.
|
|
|
|
|
If anyone is still having any trouble logging in please PM me.
|
|
|
|
|
Show Posts
