Fetching the balance of a number of addresses would be quicker using the /multiaddr API call rather than calling addressbalance individually e.g.

https://blockchain.info/multiaddr?active=19BgLUEFhKAxbcELVMafbvZb4RCzGAkraa|1A8JiWcwvpY7tAopUkSnGuEYHmzGYfZPiq

If you don't want transactions included add a simple=true parameter as follows:

https://blockchain.info/multiaddr?active=19BgLUEFhKAxbcELVMafbvZb4RCzGAkraa|1A8JiWcwvpY7tAopUkSnGuEYHmzGYfZPiq&simple=true

Looks like a good concept.

If the screen is large enough the search box should be shown in the top right. If it is too small it should be shown on the main page, or do you not see it at all?


So the answer to that question is, because blockchain.info is buggy Should be fixed now.


Added now. the push_tx function from https://github.com/blockchain/My-Wallet/blob/master/blockchainapi.js may be of some use.

------

- Android updated with the ability to scan watch only addresses + other improvements to the address book.
- New paper wallet tutorials http://blockchain.info/wallet/paper-tutorial & https://blockchain.info/wallet/paper-wallet-tutorial-web

Try this:

Go to “Preferences… > Advanced > Network > Offline Storage”
Click on “Clear now”

I agree but the problem is it wouldn't get accepted into Google Play.


Can do.


Should be back now.

------

Changes

- Better paper wallet generator



- All new wallets will have an option of printing a paper wallet on the sign up page
- Ability to generate a cold storage addresses on the receive coins page. It will generate a new PK, open a paper wallet specifically for that key and then add the address as watch only. Best used with one of the browser extensions.

Also, I am seeing some "Non-canonical signature" errors in the pushtx logs. Anyone receiving this error please report what client you are using.

It is a caching issue, if you normally login using the direct link to your identifier try https://blockchain.info/wallet/login instead.

Top right.

A note can be added by the person who submits a transaction to blockchain.info which hasn't been seen on the network previously. Signature verification using a signed message is better because a) you are trusting that blockchain.info is not lying to you b) a transaction could be intercepted very quickly from its true originator before it reaches our node and manually submitted to us including a note.

But it does serve a reasonable proof if you are ok with the above.

Those non-standard signatures should have been fixed a while back. I don't think it is the web interface producing those, possibly another client using /pushtx or an old iphone app. I've added IsCanonicalSignature() checks to the javascript signer and /pushtx which will be deployed in the next update all the signatures I tested produced with the web interface and android app passed but will have to wait and see if anyone starts complaining, regardless those transactions should not be broadcast anymore since the majority of nodes will rejected them.

Added in the latest version (Needs to be set in Account Settings).

Please clear your browsers cache and reload the page.

I suspect it could be done with a native client plugin but if it needs to be dependant on a native plugin then it might as well just be a standalone desktop lite client. May be some time in the future but for the moment my priority is to revise the iphone app and then get multisig working and/or support for a hardware wallet.


I think this is just a limitation of Bitcoin-Qt though? if the client tests both the compressed and compressed version of the key signing should be possible. The correct pub key will now been shown now.


Usernames were spidered from signatures on this forum and since you can put anything in your own signature it isn't good verification. Notes also be added when a transaction is submitted to blockchain.info which is slightly better proof because because the person that submitted it is likely to be the signer, however it still not 100% verification. You can sign and verify a message in the web interface.

------

Changes:

- The mnemonic phrase now encodes both the wallet identifier and password and can be used to restore a wallet at https://blockchain.info/wallet/recover-wallet

- Blockchain.info will not be enforcing the new 54uBTC minimum output size. However the transaction creation routine has been altered to avoid creating any change outputs less than 0.01 BTC, using more outputs if necessary. This will avoid none standard transactions being created accidentally as defined by the new Bitcoin-Qt rule. The apps will also need adjusting.

- mBTC display can be enabled in account settings

- You can no longer add an alias without first verifying an email address.

MAy be you have got wallet identifier mixed up? Did you create more than one account?

What is the intended usage?

I responded to your ticket previously, you did not provide the correct information.

Please try rpc.blockchain.info as the host.

P2P Fallback mode in the android app

The android app now includes to ability to switch between using blockchain.info's servers to retrieve information about transactions and the bitcoin p2p network itself. When P2P mode is enabled the app will switch to using bitcoinj as an SPV client and once it has synced the block headers you can send and receive transactions even if blockchain.info is offline. It can also be used to verify your wallet balance independently of blockchain.

- In P2P mode you cannot generate new addresses (since the wallet can't be saved on the remote server)
- Watch only addresses will not work
- If the app cannot connect to the PIN server the password will need to be re-entered every time the app launches.




I'll get that fixed tommorrow.

You are receiving a "Number of addresses must be between 1 and 1000." error through the web interface? How many active addresses do you have (list on the receive money tab)? Are there any other javascript errors in the console?

It doesn't need to be used on the network because the public key can be derived directly from the private key (which the JS interface has access to). How did you convert the pub key to an address?

If it is for a watch only address then it may be a bug.

On the addresses tab using the Actions button there should now be and option to Show the public key.

Is it all notifications you are not receiving or a specific type? If it is all notifications your public keys may not have synced with the server correctly, try generating a new address.