jcalfee

yes, keystore.getPublicKey and keystore.getPrivateKey https://github.com/EOSIO/eosjs-keygen/blob/master/API.md#module_Keystore here are example keyPath parameter: 'owner', 'active', 'active/mypermission' ref: https://github.com/EOSIO/eosjs-keygen/blob/master/API.md#keyPath

Add `keystore.deriveKeys({parent: keys.masterPrivateKey})` before you call `getPublicKey("active/1")` .. It will be interesting to see ideas in how roles are used..

Here is a use-case showing how the roles, keys, and page navigation interact: https://github.com/EOSIO/eosjs-keygen/blob/v1.3.2/src/keystore.test.js#L424-L443

In the `uri rules history` test `pathname` represents the browsers location bar: https://github.com/EOSIO/eosjs-keygen/blob/v1.3.2/src/keystore.test.js#L224-L253

>i don't keep keys in storage at all. should i care about uris? No you don't need this library then.. Have a look at my comment here, please let me...

Updated README https://github.com/EOSIO/eosjs-keygen/commit/02cea2f79e05a704a9430a933d003574eb6ebb41

It was designed to go like this: `master.getChildKey( 'owner').getChildKey('active').getChildKey('1').toString()` Owner is the parent of all keys including active.. Active is the parent of all custom permission keys.. I am not...

t1readonly.eos.io does not exist anymore .. You'll need a local node .. There is a jungle testnet but I'm not sure what the status is..

This looks pretty cool: http://dev.cryptolions.io/ discussion: https://forums.eosgo.io/discussion/493/jungle-testnet I'm looking for a URL that we can put into `config.httpEndpoint`...

From what I see, there are several different encrypted message schemes. How about deprecating this in eosjs-ecc then removing it? The shares secret can still come from eoejs-ecc.