Made a pull request: https://github.com/jim618/multibit/pull/25


Sorry only read this message just now. I didn't notice jackson and added json-simple as a dependancy, if you would like me to modify the patch I can do.

Multibit is looking great btw.

A quick way to check if double encryption is enabled to to login -> click [Import /Export] -> [Continue] -> [Export Unecrypted]. If a password dialog doesn't popup then double encryption is not enabled.

Jim, I'd like to make a patch for multibit to import blockchain.info wallets. Is https://github.com/jim618/multibit the latest source tree?

Yep, good ideas. I've added them to the todo list. Thanks.

Here two new graphs for now:

Estimated Blockchain size (Not including database indexes)

My Wallet Transaction Volume

If a malicious admin is reading your emails you've probably got more pressing security issues than loosing a few bitcent.

The key could be encrypted with a shared password or pin but then you loose all convenience of a simple email. When talking about small amounts the benefits out way the risks in my opinion.

What do you think of this:

The email only contains the partial email address of the sender:

you have been sent bitcoins from w_ll_t@_l___h__n.info

When claimed it asks what is the full email address of the sender and the user has to fill in the missing letters. e.g. in this case

wallet@blockchain.info

You can now send bitcoins via email:

Simply enter one or more recipients into the to field:



An email will be sent to each address:



Follow the link in the email to claim:




How it works:

- The javascript generates a new bitcoin address for each recipient, then sends the funds to those addresses.
- The newly generated keys are stored in your wallet.
- An email containing the private key is sent to the desired email address.
- When "claimed" the key is swept into a new bitcoin address.

Usage Notes:

1) The key is not stored on blockchain.info's server, but it does pass through it (SMTP).
2) The sender can reverse the payment at anytime if not claimed. To reclaim check your archived addresses and sweep the key labeled 'Sent to $email'
3) As email is not particularly secure this is intended for small amounts and will refuse to construct a transaction over 20 BTC.

I think this would be confusing. You could use the new sweep feature, might be easier.


Thanks Ian, would have been good to have another Brit there.

----

Blockchain.info now has an agreement with Eligius to process low fee transactions - which hopefully means no more "stuck" transactions. I will be monitoring for any possible transaction spam.

Thank you to luke-jr for sorting this out.

v. 1.9.3 now on Cydia - Mostly bug fixes + The ability to scan keys from a paper wallet.


I could add a logout button which would require you to enter your first password again? Might bit a bit must to remember a first password, pin and second password.


I've removed the secret phrase from the mobile wallet page.

** There was an issue earlier today where transactions would not show for some accounts. This is fixed now. **


I tried to implement javascript message signing but can't figure out how to verify the signature. Could someone with bitcoind check if this message verifies:

Address: 1AJbsFZ64EpEfS5UAjAfcUG8pH8Jn3rn1F
Message: test
Sig: MEQCIJXCh4F4PxiuGXb1h+G/0t5+QfvvR+qpulIrhwM3/ZHfAiDStGbU9sy8kg96iNhTMdV3O6eaB1DM5ppkke9t2Pkn3A==

I think as the mainline bitcoin client uses a compressed sig it won't work.




Are they not interchangeable? Most clients seem to respect both.


Ok I see what you mean, will fix.

P.S. Just found out today Me and Brian Armstrong (http://bitbank.is/) have been accepted for an interview for YCombinator. Our proposal is working on a bitcoin wallet with mass-market appeal i.e. PayPal with bitcoins. I don't know how this fits with blockchain.info yet but if we get some seed investment and publicity it could be the start of something good.

What are the use cases?


Thank you for the enthusiasm I am really pleased with how it's coming together. There is still a lot of room for improvement i.e. the wallet cannot function for long without blockchain.info (as the transactions list won't update). I'm looking at using stratum as a fallback.


Fixed


It's designed for noobs, it want that form to be simple as possible. You can construct a URI request for a specific address on address pages.


Where do you mean? On the two-factor authentication page?


You can use blank space.


All should be fixed in the new version (not released yet).


It uses the 24hr rate from http://bitcoincharts.com/t/weighted_prices.json - 15m or realtime would be better.


Nice ideas. I intended to redesign most of the android app at some point and will incorporate them then.

New Features

* Bulk delete and Sweep of archived addresses.

* Auto-detection of private key formats.
* Logout button.

No need, the Site isn't going anywhere, I'd rather see growth at the moment.

Thank you to the recent donors though.

New Feature - Full offline mode

My Wallet can now function even when blockchain.info is offline. Using html5 offline cache all javascript, wallet and transaction data will now be temporally stored in your browser.

This means even if our servers got seized tomorrow you would still be able to access your wallet and move funds elsewhere.

To Test:

1) Login to My Wallet as normal.
2) Disconnect your internet
3) Now refresh the page and the site should still load.

Usage notes:

** Does not work when two-factor authentication is enabled as that would defeat the purpose.
** If you want to disable this feature enable private browsing.
** The Unspent outputs cache can be invalidated if you are using alternative clients (including the blockchain iPhone / android app).
** It is still recommended you keep regular email or dropbox backups.
** Without blockchain.info an alternative method is needed to broadcast the transaction. Currently the only service that offers this publicly is bitsend.rowit.co.uk - please consider a donation to keep this Site running.

Yep thats the plan.

If you have the Cydia version don't switch. But if you have 1.0 from the Korean store remove it and upgrade (Login through the web interface first).

Android App: 318 total installs, 211 Active installs
iPhone App:  ~250 downloads on Cydia
Wallets: 6,450 - No way to tell how many contain BTC - transactions.
Traffic: 12th April 3,624 uniques, 322,941 Dynamic Requests - 314 GB bandwidth in the last 30 days

I'd like to hear some stats from exchanges other than Gox, Casinos and Merchants if any care to share.

http://status.blockchain.info/500250 or http://blockchain.info/status_check will now show if there is any service disruption. The script compares the latest block height with blockexplorer and checks the websocket api is running.

I'm not sure about subscriptions. If people find the Site useful donations are always welcome.

Thank you for the feedback. If you find any glitches please report them.


Molec, does 1.9.2 fix the issue?

You can enable email alerts and double encryption in the web interface.

Having it actually in the app store is great for promotional purposes, web apps just aren't quite the same.


No that button is shown only in Cydia. But the image is still bundled with the app, perhaps they think it might be activate later.


I got one this time. Thanks for your help.


Seems there is a divide by zero somewhere. Shouldn't be too hard to find.

This is the latest rejection (for the Korean app store only).


I tried to explain the app deals in bitcoins only and does not allow trading but I guess the definition of "encourages an activity" can be quite broad. They also declined the app for the same reason without send functionality.

New payment request screen available on address pages which you can use to construct a bitcoin URI.

I don't really know what else to try. I've tested it an old iPhone 3G (iOS 4.2.1) and a 4G (iOS 5.1) and cannot replicate it. Is it possible you could try and get one more crash log?


Thanks, I'll take a look.


Unfortunately not. I'm trying to get it approved but apple just doesn't like bitcoin.


1.0 is probably a lost cause.