0 Members and 1 Guest are viewing this topic.
Quote from: xeroc on March 01, 2016, 08:53:55 pmThe answer to your question is: Yes. The current web wallet does it the same way. The private key never leaves the browser on the clientsideI think we'd better have native library for Android and iOS. If we restrict ourselves in "wallet", current state is okay IMO. But if we want to expand our services to the blue ocean, we need native libraries.
The answer to your question is: Yes. The current web wallet does it the same way. The private key never leaves the browser on the clientside
Quote from: jakub on May 31, 2016, 07:40:45 pmQuote from: kenCode on May 31, 2016, 07:04:27 pmIt is native android so it runs extremely fast.Is it native Android connected to the hosted wallet infrastructure of the OpenLedger server?If so, does it mean you've ported the whole client-side JavaScript code-base to native Android? Ported, no. This has been written from scratch. You guys can see the code in a few weeks when I upload everything to github for forking etc
Quote from: kenCode on May 31, 2016, 07:04:27 pmIt is native android so it runs extremely fast.Is it native Android connected to the hosted wallet infrastructure of the OpenLedger server?If so, does it mean you've ported the whole client-side JavaScript code-base to native Android?
It is native android so it runs extremely fast.
Can mobile users connect any graphene websocket server, and send transactions with having their private keys only in their devices?Do we have such APIs? (or kind of develop infrastructures)