Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUse long derivation paths for App Private Keys (courtesy of blockstack.js) #1496
Conversation
|
I've expanded this PR to use |
|
Because |
|
This is updated to work with the latest from this PR: blockstack/blockstack.js#433 I recommend testing this by restoring an old account, logging into multiplayer apps (which should continue to work with the same app private key that you used before if you had previously logged in) and single player apps, and by creating a new user and logging in and out of apps. |
markmhx
commented
Mar 19, 2019
|
Nope -- as far as I understand, we still are using the short app derivation paths. |
markmhx
commented
Mar 19, 2019
|
@kantai What's the main benefit here? Stronger security or? |
Yep -- this would increase the security of the app-derived keys. |
markmhx
commented
Mar 20, 2019
|
@kantai Sounds good – it seems this PR is almost across the finish line and just needs a bit more testing. Is that the case? I'm moving this to the backlog so we can prioritize for the next sprint assuming that's the case. |
|
Unless I'm mistaken, this is not backwards compatible with single-player apps, because they aren't in the |
kantai commentedJul 3, 2018
This adds support for longer derivation paths for app private keys (#1367)
This maintains quasi-backwards compatibility by
appskeyTo test this, you'll need to
npm linkin the wallet support branch onblockstack.js(ordeveloponce it's merged).