Quote from: GoldenEye on March 17, 2016, 07:48:17 AM

Quote from: fixcrypt on March 16, 2016, 03:16:16 PM

Quote from: LiskHQ on March 16, 2016, 03:09:05 PM

Fixcrypt from the Lisk Chat just showcased a Dapp lite client, separated from the full client. It can run anywhere, without having Lisk installed.

Yes thanks LiskHQ, I'll push the whole source on github later today. This is simple so far with a few bugs around the edges, but sufficient I hope to show the potential of LISK. I started to work on it yesterday. It tells you how fast you can set up something with LISK.

http://i.imgur.com/SfRZLkE.gif

Awesome, fixcrypt! It is amazing how quickly you have created this example.
Please post here (or better in the Lisk forum) the link to the sources.
I would have still two comments:

It seems to be not a light client (in terms of security), so the transactions are not localy signed. Rather, it seems to be a remote GUI for a externel Lisk node (usage of the node API). In addition, each user must be aware of the fact, that he shares the passphrase with the developer of the client. You have to trust the developer absolutely.
Node URL: only encrypted connections or connections to localhost should be allowed

Hi goldeneye,
Sources are coming, i am polishing the android light client

. Note that this is a DAPP light client, not a LISK light client. Hence the security issue.
1. Yes, for security, so far the passphrase is stored inside the client and then each time a transaction is made, it is sent to the API. This is a known limitation of LISK so far and we are already working to come up with a solution with the LISK team. This is not trivial.
2. Yes, but as a start this is enough.