You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I finding the current page for "derive keys" for Ethereum & Tezos confusing because they list: Private HD Key, Private Key -> Public HD Key -> Address. We should [i] document the difference between these and make sure we're prominently listing the ones most likely to be used by the users of those coins.
And why is there a Public HD Key, but not a Public (non-HD) Key to go with the Private (non-HD) Key?
Just a little documentation & organization might make this more usable.
The text was updated successfully, but these errors were encountered:
After some discussion of this, I think this is an important usability issue.
We need to imagine that an inexperienced user comes to GST as one of the only places that they can backup their seed and simultaneously generate addresses and keys for use with Ethereum or Tezos.
What do they actually need to see on the derive keys page? What will they need to use? And what is extra that might be possibly hidden beneath the developers-feature set or otherwise moved away?
This is both a real-world issue and a question of what best-practices we want to embody.
I finding the current page for "derive keys" for Ethereum & Tezos confusing because they list: Private HD Key, Private Key -> Public HD Key -> Address. We should [i] document the difference between these and make sure we're prominently listing the ones most likely to be used by the users of those coins.
And why is there a Public HD Key, but not a Public (non-HD) Key to go with the Private (non-HD) Key?
Just a little documentation & organization might make this more usable.
The text was updated successfully, but these errors were encountered: