Thanks for the review, @matt608! I'm not sure I understand your suggestions. Are you referring to the faucet website? If so, I'll be sure to pass your thoughts on to Valentine, who maintains the faucet.

is import function for full client json import or just for importing old light wallet .json!?
I can't remember of creating a 8-12 words key phrase!

The light wallet doesn't deal in JSON dumps for backups. Your backup is the master password it asks you to write down after you create an account. No other data is needed, and in particular, no files need to be safely stored, at least for now.

The import function is only for importing old accounts you used in the light wallet. I'll add some other import options in the future.

And please be patient during a brief interruption of service... I have to reboot my server, for an unrelated reason... Rest assured that no stake will be harmed in this procedure, and your light wallet should reconnect automatically when the server returns to operation.

Hello, world! To kick off this new week, I'd like to announce the beta release of my lightweight wallet on the BitShares network (already tested on DevShares). Currently I can only build on Mac, though I can also confirm it builds correctly on Linux as well (and some report that it works on Windows, but I can't test this as I don't have a Windows machine). So if you're not on Mac, you'll have to do your own builds or share someone else's.

I am happy to report that the light wallet is working correctly with ShapeShift.io! This means you can move directly from BTC or some other altcoin to BTS or BitUSD without ever indexing a blockchain! Cool, huh? Here's a screenshot demonstrating both sending and receiving from ShapeShift:



Please remember, this is still a beta release; this is the first debut of this software on the BitShares network, and that means that the software is not considered rock solid yet. I am not aware of any bugs which could lose you funds, but just to be safe, I do not recommend putting large stake in control of your light wallet just yet. And as always, this software is provided in the hope that it will be useful, but without any guarantees. I am not responsible for anything you do with it, or anything it does with you (or your money). That being said, if you have trouble, let me know and I'll gladly work with you.

With no further ado, here is the download for Mac:
Beta 1: http://ge.tt/api/1/files/6pZV4aA2/1/blob?download SHA1: ec44ee88e7c3dc847003b170784c53eee81946aa
Beta 2: https://nathanhourt.com/BitSharesLightWallet-Beta2.dmg Mirror: http://ge.tt/5YfYbAB2/v/0 SHA1: 75eb250e10a2b573fa1536b2872f53b094741d45
Beta 3: https://nathanhourt.com/BitSharesLightWallet-Beta3.dmg Mirror: https://mega.co.nz/#!PIQWBDbC!M6xe3vB1QvfitY6i9XNYGUjnkZrmVGj9bZmB0KD-zK8 SHA1: 817592d6196cd7be8ff692c7a28ee24af95353f4

• Fix transfer of UIAs
• Fix number formatting on certain UIAs

To build, use the BitShares branch of the git repo:
https://github.com/BitShares/bitshares/tree/bitshares
The Light Wallet is in the programs/light_wallet folder. To build, pass -DINCLUDE_LIGHT_WALLET=ON to cmake. You will need qml-extras from https://github.com/papyros/qml-extras and qml-material from https://github.com/nathanhourt/qml-material installed before running the light wallet.
Note: As of posting, the bitshares branch does not have all of the light wallet commits included in beta 2. Beta 2 contains LW: commits up to 368efffe06da110838c543f3bc6d1d15db58f9de
Note: Same as with beta 2; beta 3 contains new commits not yet in the bitshares branch.

The lightweight wallet does not currently support importing accounts it did not itself create. If you want to use it, you will need to register an account using the light wallet, via faucet.bitshares.org. The wallet will walk you through the steps.


For Windows users: I really am sorry I don't have a binary for you, but look at it this way: you get to use the Mac and Linux folks as guinea pigs to test it for you so that when you get around to trying it, all the bugs will be ironed out.

The unfortunate fact is that building a windows installer is significantly more difficult and error-prone than building packages for Linux or Mac (I say this as someone with experience doing all three). Our Windows team is working on it, and I have full confidence they'll have something working for us soon. I'll definitely be letting you all know once they've got something.

The upside is that once the first one is done, all the hard part is out of the way and the rest will simply be swapping out the binary and re-running a script. Future releases will be much faster.

It seems that fc's decryption is adding some binary crap to the end of your brain key. Please try recovering your account using only the actual words, not the junk at the end. And to echo what arhag said, These accounts are now compromised (you've published your brain keys) and should never be used for anything but testing.

arhag: Needing to restart the client after restoring is a known issue in previous versions, but I haven't seen it in the latest version. Is your build up-to-date? Same with missing transactions in the history; that should not be happening anymore. In particular, try dragging down the history view to refresh it, and let me know if that pulls in the missing transactions.

As a matter of fact, I've redone the persistence framework, so you'll either have to regenerate from your brain key, or manually copy the data to the new storage, after upgrading to the version. I have yet to write the data portability code, sorry about that.

So note to all: make sure you've got a copy of your brain key before upgrading, if you want to build your own. I'll make an update utility if people need it, but for now it should be a simple matter of reloading the account from backup.