Couple of issues with addresses generated on Saturday not being monitored correctly. All transactions should be forwarded correctly now, apologies for the delay.

Bitcoind, just with some modified networking code.


The private key returned by /new is Hex encoded and the compressed address is shown. The merchant API should be compatible with no conversion however using the call where you pass in a single private key only the uncompressed address is checked. Now both the compressed and uncompressed balances will be check and it should work fine.

If you have sent payment withe the correct identifier it should not matter.

PM me your reference number if the payment has not cleared in an hour.

Apologies for the downtime again. The site was moved to a dedicated rack and a new server installed https://i.imgur.com/jl5uVlc.jpg

Updates can normally be found on twitter https://twitter.com/blockchain

The API and web interface work with the same wallets so if you import a private key using [Import / Export] in the javascript interface it will be available in the API as well. If you would like to import a key programatically you can use the importprivkey method from http://blockchain.info/api/json_rpc_api

Here is the raw data from http://blockchain.info/ip-log

http://dl.dropbox.com/u/58484379/bitcoin_ipv4.csv (Warning large file: 140 MB)

ipv4 is a unsigned int representing the ip address
last_connected is a unix timestamp
ignore counter
lat, long, city, country determined using http://www.maxmind.com/en/city

Should be possible to analyse it using http://vis.stanford.edu/wrangler/ or http://www.tableausoftware.com/products/public

This issue should be fixed now.

Yep, Fixed.


I have rebroadcast them and they have both confirmed now. Perhaps an issue with automatic rebroadcasting.


Ah for some reason I disabled this. It is enabled again now but has a bit of catching up to do.

-----------

Scheduled Maintaince

Friday 22nd 10:00am approximately 30 minutes.

I know there has been a fair amount of downtime recently but in the interests of improving the situation a bit more downtime is unavoidable. An additional server is ready to be installed but there isn't enough space in the current rack. The servers will therefore be moving to a dedicated quarter rack, which means more room for future expansion and a private locked cabinet for improved security. It should just be a case of powering down and up again so it will probably be less than 30 minutes.

It maybe an unconfirmed transaction or just different was of displaying the results.

What is the bitcoin address?

A wallet.dat can only be imported into a fresh wallet:

https://blockchain.info/wallet/import-wallet

You might be confusing the blockchain which is a distributed database which holds a record of every bitcoin transaction and is sort of where btc comes from and the website blockchain.info which amongst over things displays information about the blockchain database.


Yes. Nothing, unless you have a wallet host at blockchain.info in which case a wallet backup can be imported into another client and be up and running again fairly quickly.

Correct. You can delete a private key by Archiving the address then clicking the red delete private key button (see: https://blockchain.info/wallet/wallet-faq). Read the warnings carefully though.

Exporting private keys normally doesn't mean removing them, it means copying them into another wallet but also retaining the original (either as a backup or so both wallets can be used simultaneously). If you mean deleting the private keys, then yes, once the mobile app next syncs the keys will be removed from the mobile wallet as well.


Yes the wallets are shared between both. Blockchain.info acts a bit like dropbox every device that connects using the same identifier can download the wallet, modify it and upload it again.


Wallets are always synced online with blockchain wallets, the avoids the problem of loosing your phone. There are other mobile apps which keep only a local copy.

https://bitcointalk.org/index.php?topic=40264.msg490783#msg490783 is the main blockchain thread.

A script from this transaction: http://blockchain.info/tx/d85d548b86453a32e145a554edea50e696ecb158e26d9f118f8b23657eb11f1a?show_adv=true was missing. The problem should not occur again now.

Please try again now.

The SSL cert for coinad should work correctly now.

Freaking My Cluster is driving me insane.

All the recent downtime (apart from the ddos) has been scalability problems with the database. Basically another server is needed to run a "management node" independent of the 4 existing "data nodes". A new server is ready to be installed, probably on Friday.

Fixed.


Yep a custom transaction submitted to /pushtx. Bitcoinj validates scripts but custom validation has to be done to match the inputs and outputs etc, this was missing: