Looking at your PHP snippet the problem is JSON strings should be enclosed with double quotes " rather than single quotes '

e.g. as follows:


Response:


----

The reality is if you want top notch tech support then you need to pay for it, blockchain's APIs are free.

What is the problem you are having?

The SSL cert for coinad should work correctly now.

A new dialog has been added to better explain "No free outputs to spend" and "insufficient funds" errors. A dialog will popup with the option of automatically adjusting the transaction value:

The problem here is the wallet is still cached in your browsers local storage. If the browser already has a local copy of the wallet validating the code with the server is surpufulous. When two factor authentication is enabled the local storage will now be properly cleared, you may need to clear your local storage manually though.

If trying to login with another browser the code would have to validate properly, it is just caching in your own browser which is allowing it to bypass validation.


I have responded to your ticket now.


This is cloudflare showing you a challenge page which contains unverified javascript. Until the site moves off cloudflare the validator will continue to display errors.

Please use one of the packaged extensions instead https://blockchain.info/wallet/browser-extension


I have added a tool to help you debug this issue. The server will now log the response of every callback and you can view the logs by entering the callback url on https://blockchain.info/api/api_receive or https://blockchain.info/api/blockchain_wallet_api.




Ok I understand this problem better now. The outputs are in fact all unspendable. Before this 0.7/0.8 fork there had never been a very long chain of double spends confirmed in different branches, the code was not checking back far enough to the start of the fork.

http://blockchain.info/unspent?active=12U63dueaNH1ANWLe2XWF6uUqNnstyNi6c%7C138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr%7C149PQjaoTXLBkcX5wczcs947zcUbgTUdxp&format=html


Fixed, thanks.

-------

Insufficient Funds Error

some users are still have issues with Insufficient Funds errors mostly due to the miners fee pushing the value of the transaction high than the amount available. Now a new dialog will popup with the option of automatically adjusting the transaction value:

Ok Well there are two separate errors here.

For the "insufficient funds" error what is exact message? (either screenshot or copy and paste it). There is 0.5285289 BTC available to spend but the fee may be pushing it over.

The [ReferenceError: Bitcoin is not defined] is a javascript error normally indicating that a javascript file failed to load. Are there any other errors in the javascript console? Or try https://chrome.google.com/webstore/detail/my-wallet/djjkppdfofjnpcbnkkangbhanjdnoocd?utm_source=chrome-ntp-icon

Please try clearing your browsers cache and reloading the page.

http://www.wikihow.com/Clear-Your-Browser's-Cache

Can you link me to an example transaction that the fee should be higher.


The new server is still not in yet. But I have enabled profit/loss again now.

-----

/pushtx is now using Bitcoinj to validate transaction scripts rather than Bitcoind. This means as soon as the /pushtx sucessfully responds the transaction is guaranteed to inserted into the blockchain.info database. Previously /pushtx would do some preliminary checks and then hand the transaction over to Bitcoind for full validation.

In addition to the improvements yesterday, transaction creation using the api and wallet interface will now be much quicker and more reliable. "Error getting Unspent Outputs", "Insufficient funds", "Error Pushing Tx" should all be fixed.

I replied just above. 17Wt5vmidhegUGXFiyiuQYc21QPb8rMYnC has a balance of 0.20027549 BTC.

Nice article.


I would not validate by ip address anymore.

- Use a hidden callback URL.
- Use a secret parameter when the address is generated and validate it is the same in the callback.
- Call /q/txresult to validate the amount received by a transaction matched that being reported by the callback. (Example in doc).


How do you mean preventing you from logging in? What is the error?


Thank you for the report. This will be fixed shortly.

I think may be your secret phrase is is incorrect. Please PM me.

I responded to your post in the main blockchain thread yesterday.

Most errors related to this issue should be fixed now. Anyone still experiencing this problem please PM me your bitcoin address(s) and the amount your are trying to send.

The balance of the address 19drtjVi2Q5qXT6TFzf3XCGw3LEYtsMwZg is 0 BTC. Therefore I assume the problem has been resolved? Please PM me if it isn't.

"No free outputs to spend" means the balance of an address is zero.

This issue with this warning showing for addresses with a balance greater than 0 should be fixed now. However anyone still experiencing this problem try visiting:

https://blockchain.info/unspent?active=$address&format=html

Replace $address with the bitcoin address you are trying to send from. Check for any warnings.

With the browser extension it would be impossible for them to alter the javascript. In a couple of days the site will be moving off cloudflare instead using several nginx proxies (http://blog.unixy.net/2010/08/the-penultimate-guide-to-stopping-a-ddos-attack-a-new-approach/).


Looking at the addresses in your wallet there are many double spends which has caused the blockchain interface to get confused somewhat. I assume you are are using another client also?

The balance of 138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr is 1.309424 BTC, the other addresses are zero.

There are several transactions that were confirmed in the major fork a few days ago but have not confirmed in the new chain for some reason. Normally these transactions would be pruned however since they are already included in an orphaned block they cannot be removed, this is unusual and I'm not sure why they are not confirming. I have rebroadcasted them several times but it doesn't seem to have helped, the best course of action would be to double spend them with another client.

The following page shows which double spends in your wallet are unspendable:

http://blockchain.info/unspent?active=12U63dueaNH1ANWLe2XWF6uUqNnstyNi6c%7C138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr%7C149PQjaoTXLBkcX5wczcs947zcUbgTUdxp&format=html


There is 0.20027549 BTC available in address 17Wt5vmidhegUGXFiyiuQYc21QPb8rMYnC. Is there another address?

Please try clearing your cache and reloading the page.


The address has received an output but the result of the transaction was < 0. This will happen when change is returned to the same address. I would just ignore any values < 0.


Apologies this was a bug I introduced last night, and should have been fixed this morning.


Yes this is correct.

-----------

The default display filter for address pages has been changed to "filter unspendable" which means double spends and transactions not confirmed in the main chain (apart from recent unconfirmed transactions) will be hidden. This means balances displayed on /address will be much more accurate of representation of the of the balance of an address even if it has received double spends or has received payments from an orphaned block.

If we use btctrada's address as an example:

"Filter Unspendable" shows a balance of 1.309424 BTC - http://blockchain.info/address/138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr

Viewing all transactions (Old default) shows a balance of 194.73778528  BTC - http://blockchain.info/address/138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr?filter=0

Filtering by confirmed only shows a balance 0 BTC - http://blockchain.info/address/138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr?filter=5

Wallet balances have always defaulted to "Filter Unspendable" however a bug has been fixed preventing the children of unspendable transaction being properly filtered (occurred when there was a chain of double spends).

Database improvements

Previously when a wallet reached about 10k transactions fetching the balance and creating transaction would become a little slow. This has now been fixed and the speed of all the major API calls has been improved. This transactions should be very quick to construct regardless of the size of the wallet.
 

What is the error you are receiving?

These should all be repaired now.

Something similar to this?

https://blockchain.info/unspent?active=1A8JiWcwvpY7tAopUkSnGuEYHmzGYfZPiq&format=html

Sending by SMS/Email works by generating a new private key, saving that key in your wallet and then mailing a copy of the private key to the recipient. That way both sender and recipient both have full control of the funds until one of them send them elsewhere.

If you look in Archived addresses there should be an address label "Sent Via SMS/Email to XX". If you sweep that address the funds will be reclaimed back into your own wallet.