Blockchain.info - Bitcoin Block explorer & Currency Statistics

[osmosis]

.

[slothbag]

Can you upload the version you got running and post a link. I will make a .deb for it and put it on myrepospace.com so it’s available to others using Cydia if you do. My download must have been faulty. I was never able to get it to compile and make the .app to run properly. I messed with it in iFile for hours.

Here ya go..

http://www.filefactory.com/file/25y0t5k5qtav/n/Blockchain_ipa

Edit: It's not signed, so you'll obviously need code signing disabled/bypassed for this app to work on your phone.

[piuk]

Here's the latest from apple.

We are currently reviewing an app that you submitted for inclusion on the App Store, and want to let you know that the review process will require additional time. We apologize for the delay and will provide you with an update on the status of your app as soon as possible.

At least they are considering it. I do have the app packaged for Cydia but don't want to publish a link yet incase it interferes with the review processes.

[molecular]

Hm, the android app is not compatible with my phone (this is true for all of the "light" android apps I've checked).

Would it be possible to make your android wallet work for android 2.1? (I can't upgrade, lowly phone)

[Stephen Gornick]

When did the "SMS Phone Deposits" feature get added?

 - https://blockchain.info/wallet/sms-phone-deposits

[Matthew N. Wright]

When did the "SMS Phone Deposits" feature get added?

 - https://blockchain.info/wallet/sms-phone-deposits

Not sure, but I would recommend that the OP be careful getting into the business of sending Bitcoins for SMS/phone.

Even DialCoin is a dedicated site with state of the art fraud prevention technology and we only work with processors who are worth the trouble, but still we get constant fraud attempts, chargeback attempts, etc. It's all part of the scammers game. If we didn't have the experience and knowhow we do, we'd be bankrupt because frankly speaking SMS for Bitcoins is a high-risk, non-viable business in itself. Even DialCoin has had to make some tough decisions to decrease risk (which unfortunately decreases some functionality as well).

The payment processor they are apparently using, Zaypay, is one of the many payment processors DialCoin looked into about 6 months ago and we found their terms to be dangerously risky and easily defrauded. I say this with the utmost respect for Blockchain.info (because I think it's a fucking kick-ass service):

You have no idea what you're getting into.


EDIT on April 1st, 2013: Now a year later, I noticed that you are no longer allowing BTC to be bought by SMS. I won't jump to conclusions as to the reasoning for this, but I am happy that you removed that risk factor from your site.

[piuk]

I am not sure if this is a known bug, but I noticed that the wallet functionality of blockchain.info isn't dealing well with an orphaned block.

This should be fixed now.

Would it be possible to make your android wallet work for android 2.1? (I can't upgrade, lowly phone)

Sorry I can't get it running on 2.1 because it depends on java.util.concurrent which isn't available in the old SDK.

http://blockchain.info/address/413933fcb38a35c33bd5b4b606d09ad27b8e0448

This happens when my node doesn't receive an "inv" message. Normally when the transaction is directly included in a block rather than being broadcast.

When did the "SMS Phone Deposits" feature get added?

 - https://blockchain.info/wallet/sms-phone-deposits

A couple of days ago. I am just testing the waters a bit which is why I didn't announce anything.

You have no idea what you're getting into.

Well I can lose more than I sell and i'm only selling what i'm comfortable risking. Dialcoin doesn't work for me, I don't see anything on the select payment method page.

Maybe some of you who have been following this thread for a while will remember that the site started as a single html page with one or two statistics on it. Since then I've kind of just been adding new features just because I like the technology, not really expecting it to go anywhere. Recently has been the first time I've thought maybe the Site has more potential, so I'm exploring new ways to monotenize it. I don't mind loosing some of my own money, as long as customers money is safe.

[Matthew N. Wright]

I don't mind loosing some of my own money, as long as customers money is safe.

Good attitude! I totally feel the same way.

Hope I didn't come across wrong either, I absolutely love the site.

[mcorlett]

I've been using the full address API to resolve Firstbits addresses, but the request time grows linearly to the amount of transactions associated with that address. Can you add a new API method or just a small switch to only resolve the address? I get faster request times, and you reduce unnecessary server load. Win/win!

[evoorhees]

Can I just say how extremely impressed I am with the entire Blockchain.info site and the new wallet and android app. It's all fucking badass and I use it every day.

Great work x100. The property is a true asset to the community today and into the future.

[molecular]

Would it be possible to make your android wallet work for android 2.1? (I can't upgrade, lowly phone)

Sorry I can't get it running on 2.1 because it depends on java.util.concurrent which isn't available in the old SDK.

Too bad. Well, thanks for trying and getting the info back to me (us). Keep going, blockchain.info is such a great site! Incredibly fast, too.

[piuk]

Thanks everyone, I'm glad people find it useful.

I've been using the full address API to resolve Firstbits addresses, but the request time grows linearly to the amount of transactions associated with that address. Can you add a new API method or just a small switch to only resolve the address? I get faster request times, and you reduce unnecessary server load. Win/win!

You can use

/q/getfirstbits/$address

find the firstbits from an address

or

/q/resolvefirstbits/$firstbits

to find the address from firstbits

Those calls are used in the javascript client, not sure why I haven't document them.

New Version of the android app (2.

* Automatic fee calculation
* Separation between active and archived address
* Wallets should update live (i.e. any changes you make in the web interface will immediately show on the android app and visa versa - it's a bit flaky though)
* Further improvements to wallet synchronization

[osmosis]

http://blockchain.info/address/413933fcb38a35c33bd5b4b606d09ad27b8e0448

This happens when my node doesn't receive an "inv" message. Normally when the transaction is directly included in a block rather than being broadcast.

Can I suggest displaying the time the transactions block was created, so that the transaction list can still be viewed chronologically. Currently I fall back to blockexplorer to do this.

[dvide]

New Version of the android app (2.

* Automatic fee calculation
* Separation between active and archived address
* Wallets should update live (i.e. any changes you make in the web interface will immediately show on the android app and visa versa - it's a bit flaky though)
* Further improvements to wallet synchronization

https://i.imgur.com/VhkWd.png

Just downloaded 2.8 on my Galaxy Nexus but it's still having trouble paring with my existing wallet. After I scan the QR code it says 'Failed to decrypt wallet. Password may be incorrect'.

Also, when I first start up the app, before I choose between 'Pair Device' or 'New Account' on the welcome screen, it is already giving me errors before I do anything. At the bottom messages appear, saying 'Generated new wallet' and then 'Error decrypting wallet. Please check your password' and then the same 'Failed to decrypt wallet. Password may be incorrect'. This is all while the welcome is still showing.

Now I'm also getting this crash on startup sometimes:

Code:

=== collected at launch time ===

Test: false

Date: Thu Mar 29 06:41:40 GMT+01:00 2012
Version: 2.8 (86)
Package: piuk.blockchain
Phone Model: Galaxy Nexus
Android Version: 4.0.2
Board: tuna
Brand: google
Device: maguro
Display: ICL53F
Finger Print: google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
Host: vpbs3.mtv.corp.google.com
ID: ICL53F
Model: Galaxy Nexus
Product: yakju
Tags: release-keys
Time: 1323307455000
Type: user
User: android-build
Configuration: {1.0 234mcc10mnc en_GB layoutdir=0 sw360dp w360dp h592dp nrml port finger -keyb/v/h -nav/h s.23}
ScreenLayout: size 2 long 16
DisplayMetrics: DisplayMetrics{density=2.0, width=720, height=1184, scaledDensity=2.0, xdpi=315.31033, ydpi=318.7451}
Databases: webview.db webview.db-wal webviewCookiesChromium.db webview.db-shm address_book address_book-journal


=== collected at exception time ===

Total Internal memory: 14311309312
Available Internal memory: 7712460800

java.lang.NullPointerException
at piuk.blockchain.android.WalletApplication$5.run(WalletApplication.java:307)
at java.lang.Thread.run(Thread.java:856)


Contents of FilesDir /data/data/piuk.blockchain/files:
2012-03-27 03:29:30  files  [4096]
  - 2012-03-29 06:38:50  wallet.aes.json  [1244]

Contents of CacheDir /data/data/piuk.blockchain/cache:
2012-03-29 06:41:34  cache  [4096]
  - 2012-03-27 07:44:31  webviewCacheChromiumStaging  [4096]
  - 2012-03-29 06:41:38  .stacktrace  [1432]

[piuk]

Can I suggest displaying the time the transactions block was created, so that the transaction list can still be viewed chronologically. Currently I fall back to blockexplorer to do this.

This is more demanding than it sounds because it requires an extra SQL query per transaction, so that is 50 extra queries per address page. I'll see if I can cache the block times or something.

Just downloaded 2.8 on my Galaxy Nexus but it's still having trouble paring with my existing wallet. After I scan the QR code it says 'Failed to decrypt wallet. Password may be incorrect'.

I think i might have found the source of this error. I've just uploaded a new version (87), could try that and let me know if it fixes it. Thanks

[julz]

Would you consider providing a page to give a device-pairing QR code minus the password,  and a mechanism to pair by manually entering the pass?

I see the device-pairing QR contains the guid + sharedkey + password.

I thought it might be handy to have such QR codes printed out so I could easily change between wallets, but didn't like the idea of having the password included.
I assume the sharedKey shouldn't really be left around.. but isn't really much use to anyone else without the password?


Also.. what is the reason for including ones own active receiving addresses in the autocomplete for the 'pay to' bitcoin address?
It seems a little confusing. e.g  I might label one of my receiving addresses as 'Fred' for funds from him.. but it would be very easy to accidentally send to this address when I later go to send coins to Fred.
Even if you did want to send to one of your own addresses in the same wallet.. it would be better as a hidden more advanced option no?

[dvide]

I think i might have found the source of this error. I've just uploaded a new version (87), could try that and let me know if it fixes it. Thanks

Getting the same thing unfortunately.

I'm pretty sure I just this moment downloaded a new version from the Play store, but I want to make sure. This might sound dumb but where do I check if the version I have installed is 87? It still says 2.8, but I don't know if you incremented that number.

EDIT: I'm on 2.9 now but still the same error. Here's the exception report:

Code:

java.lang.Exception: Error Decrypting Wallet
at piuk.MyWallet.<init>(MyWallet.java:68)
at piuk.MyRemoteWallet.<init>(MyRemoteWallet.java:115)
at piuk.MyRemoteWallet.setPayload(MyRemoteWallet.java:541)
at piuk.blockchain.android.WalletApplication$5.run(WalletApplication.java:362)
at java.lang.Thread.run(Thread.java:856)
java.lang.Exception: Error Decrypting Wallet
at piuk.MyWallet.<init>(MyWallet.java:68)
at piuk.MyRemoteWallet.<init>(MyRemoteWallet.java:115)
at piuk.blockchain.android.WalletApplication.readLocalWallet(WalletApplication.java:519)
at piuk.blockchain.android.WalletApplication.onCreate(WalletApplication.java:165)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:969)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3925)
at android.app.ActivityThread.access$1300(ActivityThread.java:122)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1184)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4340)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
at dalvik.system.NativeStart.main(Native Method)
java.lang.Exception: Error Decrypting Wallet
at piuk.MyWallet.<init>(MyWallet.java:68)
at piuk.MyRemoteWallet.<init>(MyRemoteWallet.java:115)
at piuk.MyRemoteWallet.setPayload(MyRemoteWallet.java:541)
at piuk.blockchain.android.WalletApplication$5.run(WalletApplication.java:362)
at java.lang.Thread.run(Thread.java:856)
java.lang.Exception: Error Decrypting Wallet
at piuk.MyWallet.<init>(MyWallet.java:68)
at piuk.MyRemoteWallet.<init>(MyRemoteWallet.java:115)
at piuk.MyRemoteWallet.setPayload(MyRemoteWallet.java:541)
at piuk.blockchain.android.WalletApplication$5.run(WalletApplication.java:362)
at java.lang.Thread.run(Thread.java:856)

[Stephen Gornick]

Here are a few feature requests.

1.) I'ld like an easy way to, in My Wallet, to print just the public address and QR code for an address.  The Receive money tab does this, it just doesn't print nicely and has more than is necessary.  I would put that paper with the address in my wallet in my back pocket and hand it out to someone later (for them to send bitcoins to me).     I know I can also use Wolfram Alpha or something like that too for generating a QR Code + text but it just isn't a nice check-sized slip of paper convenient to carry around.  Here's an example:
 - http://www.wolframalpha.com/input/?i=qr+code%3A+bitcoin%3A1PC9aZC4hNX2rmmrt7uHTfYAS3hRbph4UN

  (And yes, I know the BlockChain.info mobile app for Android likely does this, but until we have 100% smartphone penetration and this app on all smartphones, there will be the need for paper-based or electronic transfer of the data.)

2.) I'ld like to be able to use a different address for notifications than the e-mail address in the "account details".  Specifically, I'ld like to have the notifications go to my mobile phone's e-mail address so that I get alerts.  Right now if I were to change the one address for the account to my mobile phone, then that is where backups of my wallet will be sent each time I click "email backup" -- something I want to do periodically.   I might even want multiple notification addresses -- so that my phone and my normal e-mail both will get payment alerts.

3.) Scheduled Wallet backups sent by email.   Can I request these be sent on a schedule?  e.g., Daily / Weekly / Monthly   (and a checkbox "only when the wallet has changes").   I know BlockChain.info stores the encrypted wallet for my account but if some day the site were to go offline (say a multi-day denial of service attack or something) I still would like access to the funds in my wallet and having a local backup copy allows me to access the wallet's keys.  So having recent backups is of value.  Not having to remember to send those manually would be a nice feature.

[dvide]

Just downloaded 2.8 on my Galaxy Nexus but it's still having trouble paring with my existing wallet. After I scan the QR code it says 'Failed to decrypt wallet. Password may be incorrect'.

It's working now. Turns out my wallet account was old and was still in some old format or something. If anyone else is having this same problem, open up your wallet in your PC browser and go into account settings and then run the integrity check. After the check (which was valid for me), pairing worked.

[piuk]

Would you consider providing a page to give a device-pairing QR code minus the password,  and a mechanism to pair by manually entering the pass?

I see the device-pairing QR contains the guid + sharedkey + password.

I thought it might be handy to have such QR codes printed out so I could easily change between wallets, but didn't like the idea of having the password included.
I assume the sharedKey shouldn't really be left around.. but isn't really much use to anyone else without the password?

Could you have the same main password for each wallet and then have a different second password for security? Typing passwords is a pain on a small onscreen keyboard if you just want to switch wallets to check the balance or something.

With the sharedKey someone can remove your wallet from the server, but can't access the private keys or anything like that.

Even if you did want to send to one of your own addresses in the same wallet.. it would be better as a hidden more advanced option no?

Yes your right, I will remove them from the autocomplete.

Here are a few feature requests.

Acknowledged, i'll see what I can do.

Updates:

** New fraud prevention with SMS deposits, only one purchase per customer per month.
** New version of the android app out. If you were getting wallet decryption errors a dialog will now popup explaining how to fix it.
** Possibly good new from apple regarding the iPhone app.