-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keystore storage query #1
Comments
Things for RN we need to plug in:
Do you have an Api reference you want to use for the 1st two? Does RN have a URL router? |
seems existing keystore use localstorage to save the keys, but RN does not support localstorage, any suggestion ? |
It should be easy to pick out local storage for RN .. However, keystore / keygen is not for encrypted storage, it still needs a secure password manager to keep the root seed. That is what I would want to look into: are their good password managers in the RN environment or does one have to build that out.. |
i am also aware of that existing keystore keep the plain private key which is not secure and also looking for the suitable solution, and one more thing is that the existing storage implementation is synchronous, but the RN asyncstorage is asynchronous, how could we plugin the asyncstorage to existing keystore in RN environment @jcalfee |
For async, |
I also have similar questions. I'm doing research on what it will take to build what I need. here's what I need to accomplish from my React Native app:
from the above, I'm not sure whether i even need the keystore. I'm imagining that when the app runs, it checks the storage and if it finds a keypair then it can sign transactions. is there code somewhere doing what I need? I can see from https://github.com/EOSIO/eosjs-keygen how to create the keypair and account but I'm wondering how everyone else manages this |
is the keystore component platform independent? we are considerring to dev a wallet app with RN, not sure whether if will be supported or not.
The text was updated successfully, but these errors were encountered: