-
-
Notifications
You must be signed in to change notification settings - Fork 17
6.1.0 #105
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
6.1.0 #105
Conversation
Co-authored-by: Maarten Zuidhoorn <maarten@zuidhoorn.com>
|
|
||
| ## [6.1.0] | ||
| ### Changed | ||
| - Update BIP-39 implementation from `@scure/bip39` to MetaMask fork version `@metamask/scure-bip39` ([#101](https://github.com/MetaMask/key-tree/pull/101)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know that it's given in the PR, but maybe it's worth explaining what the fork does over the original implementation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure can do!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done here
Co-authored-by: Maarten Zuidhoorn <maarten@zuidhoorn.com>
This is the release candidate for version 6.1.0.
[6.1.0]
Changed
bip39implementation fromscure-bip39to metamask fork version@metamask/scure-bip39(#101)@metamask/scure-bip39fork accepts secret recovery phrases inUint8Arrayformat making it possible to use more secure patterns of passing secret recovery phrases around. This change is non-breaking however, as themnemonicToSeedfunction used in this package still accepts secret recovery phrases in string format.