Updated to beta1-update1.
https://s3.amazonaws.com/limewalletdwn/limewallet-beta1-update1.apk
Fixes errors in memo handling

+5 excellent!

Hi ElMato, is this thread the best place to report bugs or do you have another preferred method. I am currently having issues when I try to deposit btc and I type in the amount. I get an error whether the amount is USD or btc. It seems to work when I look at the withdraw function though. Again awesome work on the wallet, really excited to show my friends.

Thanks for the report, a github issue is ok, but you can also report it here.

Im seeing that our main provider of BTC=>bitUSD (yunbi.com) is giving us timeout.

02:19:14 robby.1 | provider yunbi update error ... HTTP 599: Connection timed out after 20000 milliseconds

That renders the book unusable then we are unable to give you a quote.
(Note: we should alert the user better)

Im hitting them 1 time each 10s but 6 requests in parallel (5 books + balance), so maybe they dont like that frequency ... will talk to them tomorrow.

Withdraw is working because metaexchange is updating ok, and they are doing bitUSD=>BTC.
(In fact thats the only way we go with them because of the speed of BTS txs)

02:19:15 robby.1 | metaxchg update OK

Quote from: fav on August 11, 2015, 09:35:55 am

Any ETA on playstore add?

It would be very good to become popular and attract new users

Its a tricky question.

On one side we want to have a period of beta while we test our backend live and adjust details/bugs etc.

On the other side since we don't know the exact release date of BTS 2.0 we are in kind of debating if we should publish the wallet supporting 0.9.X or wait for the final BTS 2.0 ..... gauging

Thanks for the update ... still: can you not use the same seed/privkey generation algirithm used in the web wallet? This wouls make user experience alpt better. If you wish i can search the code and point you to the relevant lines

The wallet structure we use is different from other wallets because of our specifics need.
The same problem happens with many bitcoin wallets, and in fact for Bitcoin is easier to standarize a common wallet format because of the simplicity of the overall architecture.

It will be helpfull to have a standard wallet format for easy interoperability of Bitshares wallets.
Just like Bitcoin have BIP32, BIP39, and BIP44.

Thank you all for the feedback, i will try to answer some of the questions/doubts.

On BTS & UIA

xeroc
The wallet seems to only know about USD .. if I send any other asset I get an empty row in assets .. can't you pull the details from "get_asset" and post the symbol of an arbitrary asset?

bobmaloney
Question: Are you guys going to include BTS eventually, or just sticking to Assets?

sudo
can't receive  bts &UIA

It is planned.
We will add support for any UIA and BTS also.

bobmaloney
1) We should be able to add contacts directly from our send/received transaction lists (or at least from the view details screen).

2) It should probably be made more clear that this wallet holds bitBTC rather than BTC.
(I think this might frustrate or anger a user who is not familiar with the product)

3) Additionally, "balance on tap" should NOT round up from actual balance! Bad idea - rather, stretch out the decimals if need be.

1) Planned [See Contacts]
2) Good point, we will review the BTC naming.
3) Planned

Shentist
1) i wanted to save a contact, but i don't want to tipp in the public key (needs to long) why is it not possible just to put the known names into it?

2) would be nice if i can easily change the shown currency aka asset on top, maybe with a fingerslide on top i can slide through my holdings!

1) Planned [See Contacts]
2) Planned 

lafona
1) One thing I noticed though, when copying the address to a coinbase wallet on Android, it copied two slashes before the address and that I had to delete them for it to send

1) Known bug

sudo
1) can‘t output the private key & wallet json backup

2) I try to restore my wallet @https://wallet.bitshares.org/  use brain wallet  12words
but my id did't appear

can’t add contact  only use name (note: pubkey or address empty)

1) Privkey is not being shown, just the seed (will add the option in some advance menu).
   I dont undestand the "wallet json backup".
   Are you refering to the alpha1/2 backup?

2) The wallet structure is different from them one used in wallet.bitshares.org even if we both use mnemonics to generate the seed.

3) Planned [See Contacts]


Contacts

The Contacts feature was designed for those who dont want to register their name into the blockchain.
So, if i want to send to a "name" that is not registered in the blockchain i need to have it as a contact with his pubkey or address.

The use case was as following:
- User1 dont register his name in the blockchain.
- User1 => Send his contact information (QR code, mail, other) to User2 (name+pubkey).
- User2 add User1 as contact. (name+pubkey)
- User2 can now send to his "name" with memo.

But we need to rethink to also cope with the case that someone want just to have "favorites"/"recently used" names.
(just the names not the pubkey, because the active_key can change in time)

And those names should be presented first (scrollable) when the user clicks the destination field in the send window.
(In fact this is already coded, when you search in the autocomplete its searching into your local-contacts and in the global-directory [blockchain])

We will redesing that part, just need some more thinking to cope with all the use cases and to be very usable by default.

On 2.0 support

jakub
Just wonder how the 2.0 launch is going to affect your back-end code?

wuyanren
On the basis of the development of 2.0？

delulo
Wondered the same. How much work is necessary to make it work with 2.0?

2.0 support is planned and some work has been done in the dev backend to support it.
In fact it will simplify a lot of things that we are doing on our side, its just a matter of how much of owr own infrastructure we will keep and how much we will relay on the new 2.0 architecture.

Ej:
- Import only selected accounts into database => It seems there is a plugin system in the new 2.0 code that can help with that.
- Pay the network in BTS / Charge the user in BTA => 2.0 has also resolve this with the referal program.
- Memo recovery => We are using op_data inside each tx generated by the wallet to later recover the out memo, 2.0 also resolve that.
- etc, etc, etc.

I would like to have a working wallet with the 2.0 test-net as soon as we can becasue 2.0 is the future!

iOS Version
PM you email to add you to apple's testflight.

*Update1*
*Fix errors in memo handling.

Important!:
Always Backup your seed before uninstalling the app

https://s3.amazonaws.com/limewalletdwn/limewallet-beta1-update1.apk


Dear community,

 It has been a long time wihtout updates from our side, basically because we were working as hard as we could to produce a usable mobile wallet.

 So *beta1* of LimeWallet is here for you to test.



 Despite the fact that there is a lot to be done, we think it is in a usable state.

Installation from binary:

Android:
(See above)
 
iOS: [instructions soon]

Installation from source:

Go to https://github.com/limewallet/limewallet and follow the instructions there.


Features:

• Private keys on client side
• Full wallet recovery from a seed. (This include in/out memos)
• Deposit / Withdraw in Bitcoin
• Bitcoin payments
• Handling of Bitcoin urls (android intent)
• Password locking
• Local addressboook
• Send to name, pubkey or address with memo (all from client side)
• Paper wallet balance import
• Crypto operations using "standard" libraries (bitcoinj, CoreBitcoin)
• Android & iOS version

Liquidity BitAsset<=>BTC

Our backend is agregating the liquidity from:

• Yunbi
• Metaexchange (just BTA=>BTC)
• BTSBOTS
• BitShares Exchange (*1)
• btc38 (*2)

*1 Turned off until next week.
*2 Avilable, but not enough bank to be in every exchange at the moment.

We charge 0.3%, of the best price we find.
But we plan to go to 0% as we build partnerships with already established exchanges.
Bottom line is that we want to provide the best exchange rate that the market has for bitAssets<->BTC.

*IMPORTANT*

We are low on bank, and not every exchange allows us to auto-adjust our wallets (asking by API to do a withdraw) so balancing the wallets its a manual process.

If you want to stay in the safe side go for BTC<->USD , BTC<->CNY in amounts not greater that $25 until we have more liquidity.

The refund process will be addressed next week.

iOS Version:

iOS version is ready also and we are setting up everything in (the recently acquired by Apple) testflightapp.
Pablo will collect iOS devices serials numbers to produce an IPA.

Thanks for your patience!:
Please, help us test the wallet!. We need your feedback!! :


Note:
If anyone wants to recover funds from alpha1 or alpha2 wallet please PM me.
 

Excellent! Keep the good work guys