jcalfee
jcalfee
I think "from" and "to" should be of type `name` instead of `uint64` .. I have not looked at this in a while. It was replaced in eosjs 2.0 ..
No . the keystore is really special purpose. It is designed to be 100% deterministic based on a strong starting seed. An example: re-assign or add a permission to a...
A better name is "keygen" .. the local storage is a cache .. A password manager is the storage for that strong seed.
I also hear there are some needed crypto functions that will not work with RN.
The code your pointing to is in browser.js .. I don't have a RN environment setup now, I will get some feedback on this and see what I can do...
The best thing for you may be to fork this repo and make the change yourself (until I have done enough research to start changing things). You'll probably uncover more...
Things for RN we need to plug in: - [ ] Persistent storage - [ ] Secure random number generator - [ ] A location path or URI to identify...
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...
For async, `deriveKeys(params)` and `logout` are probably the only two functions that should return a promise. All the fetching may update the disk cache but it is updating the cache...
1) there is not a single network api call in eosjs-keygen .. there are however network calls in eosjs .. are you referring to eosjs? 2) eos does not have...